# Gavin Andresen
# 2011-11-20 18:04:12
# https://bitcointalk.org/index.php?topic=52008.msg625217#msg625217

Release Candidate 7 binaries are available at: @p{brk}
  @s{(link)} @p{par}

Difference between rc6 and rc7 :  rc7 does not remove BDB (Berkeley database) log/* files, because that is causing un-readable wallets on some people's machines (all the reports were from people running 64-bit version of Linux, but that might have just been coincidence@p{--} I could never reproduce the problem in any of my test environments). @p{par}

What that means:  old private keys can remain in a file on your disk even after wallet encryption, but they will eventually be removed.  Details: @p{par}

BDB closes the old logfile and opens a new one when it get close to 10megabytes big. @p{par}

When bitcoin shuts down cleanly, it asks BDB to remove any unused log files, and BDB will remove all but one file from database/log.* @p{par}

So: if you encrypt your wallet, unencrypted private keys will be in the old part of the log file. But after running for a half a day or so, BDB will close that old log file and open a new one. Then, the next time you restart bitcoin, the old log file containing the unencrypted keys is removed. @p{par}

This seems like a reasonable compromise between security and safety for now; a better wallet encryption solution for the next version of bitcoin (for example, one that doesn't require shutting down and restarting after encrypting the wallet) is a good idea, but out of scope for this release. @p{par}