Quote from: RylandAlmanza on July 09, 2011, 01:18:32 AM

Quote from: SgtSpike on July 08, 2011, 11:32:15 PM

Quote from: molecular on July 08, 2011, 11:07:16 PM

Quote from: samr7 on July 08, 2011, 10:01:20 PM

Quote from: SgtSpike on July 08, 2011, 05:58:37 PM

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1 more. This is a very important feature, whether it's exposed to end users or not.

Actually, I might have changed my mind (partly)

Exporting of a key has a problem, doesn't it: the key is still in the source wallet. There's no way to remove it, is there? Even if there is, it's easy to screw up and people will wonder where their money went.

The importing of a privkey is the part that is important for users (bitbill, import key generated with external tool like vanitygen) and this part, luckyly, poses no problems (that I can see), does it?

So how about splitting this and putting importprivkey in default, but not dumpprivkey?

I still disagree. I'd like to be able to export private keys from wallets, but really don't want to have to try to compile bitcoin again. That was a complete PITA.

SgtSpike, are you on windows? Do you have a binary with this patch that you can provide? I've been looking for one for a while.

+1 tried compiling it but mingw and vc10 dont seem to like it.