From: Alan Reiner <etotheipi@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Wallet encryption issue
Date: Thu, 10 Nov 2011 11:11:19 -0500 [thread overview]
Message-ID: <4EBBF7A7.8030708@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Sorry guys, I just realized I should've posted this to the dev list
first, before/instead of putting it on the forums.
https://bitcointalk.org/index.php?topic=51474
*I still have some of my private keys in plaintext. *I would guess that
BSDDB sometimes will "overwrite" data by just discarding a pointer to
the old data, and writing the replacement to a new location within the
file. In that case, examining the file with a BSDDB library tool is not
going to find this problem. You'll have to examine the raw binary file
as I did. Instructions for verifying this problem are in the post.
Can someone please verify that this is a real problem? (and should we
maybe remove my post until there's a remediation plan? This is problem
the best kind of problem to disclose after it's fixed)
-Alan
[-- Attachment #2: Type: text/html, Size: 1290 bytes --]
reply other threads:[~2011-11-10 16:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBBF7A7.8030708@gmail.com \
--to=etotheipi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox