user153: Now that v0.4 of the bitcoin client has encryption I've gone ahead and encrypted the keys in my wallet.  But I had previously made backups of my (unencrypted) wallet and those keys are the same keys that are now encrypted.
This gives me a false sense of security.
Is there any way after I've upgraded to v0.4 and encrypted to force all my existing keys to become invalid and then to spend to a new (encrypted) key so that even if an attacker gets ahold of my backup that my coins are safe?

user208: Bitcoin 0.5 will flush the key pool upon encryption. This means that when you encrypt a fresh wallet, none of its active reserve keys will ever have touched the disk in unencrypted form.

user105: Seems to me that the easiest way would be to create a brand new, encrypted wallet using the new client, then send all your coins to that one and forget about the old one.
(You can force a new wallet by simply deleting wallet.dat before launching the client)

153: <p>Now that v0.4 of the bitcoin client has encryption I've gone ahead and encrypted the keys in my wallet.  But I had previously made backups of my (unencrypted) wallet and those keys are the same keys that are now encrypted.</p>

<p>This gives me a false sense of security.</p>

<p>Is there any way after I've upgraded to v0.4 and encrypted to force all my existing keys to become invalid and then to spend to a new (encrypted) key so that even if an attacker gets ahold of my backup that my coins are safe?</p>
 208: <p>Bitcoin 0.5 will flush the key pool upon encryption. This means that when you encrypt a fresh wallet, none of its active reserve keys will ever have touched the disk in unencrypted form.</p>
 105: <p>Seems to me that the easiest way would be to create a brand new, encrypted wallet using the new client, then send all your coins to that one and forget about the old one.</p>

<p>(You can force a new wallet by simply deleting wallet.dat before launching the client)</p>
