public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andres Home <a86551@outlook.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Advisory: PHP library Bitcoin SCI weak key generation
Date: Sun, 27 Oct 2013 22:25:41 +0000	[thread overview]
Message-ID: <SNT151-W902926CDE9837FF83699C5820F0@phx.gbl> (raw)

For those developers who are using the Bitcoin SCI library (maybe others too, I
found two total and could only make contact with one), I would advise that you
review how your software handles private key creation.

Up until today, the Bitcoin SCI library used the Mersenne Twister PRNG or the
GMP library's PRNG directly to generate private keys. This has been somewhat 
resolved in the most recent version (October 27th), but only for the 
createNewMiniKey() function. Even if you haven't been using this library, it 
would be a fine oportunity to check your key generation functions if you do not 
interface directly with bitcoind. 

Affected keys have 32bits of entropy, possibly up to 56bits depending on the 
build of PHP, a low enough amount that would allow GPU based attacks on keys
in the lower ranges.


I do not know how many keys have been created using either function
.
I also don't share the authors optimism that this isn't an issue. 		 	   		  


             reply	other threads:[~2013-10-27 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 22:25 Andres Home [this message]
2013-10-27 22:46 ` [Bitcoin-development] Advisory: PHP library Bitcoin SCI weak key generation Gavin Andresen
2013-10-27 22:48   ` Andres Home

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=SNT151-W902926CDE9837FF83699C5820F0@phx.gbl \
    --to=a86551@outlook.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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