From: Andres Home <a86551@outlook.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Advisory: PHP library Bitcoin SCI weak key generation
Date: Sun, 27 Oct 2013 22:48:04 +0000 [thread overview]
Message-ID: <SNT151-W61AA4CD1C6C550B6166915820F0@phx.gbl> (raw)
In-Reply-To: <CABsx9T2wnvxm2YYeXiatR5FMEESRZO+FKR45NFpaVerrPzJA+Q@mail.gmail.com>
That's correct.
There's no source control so I've mirrored the weak functions.
The MiniKey function:
http://pastie.org/8435726
The PrivKey function:
http://pastie.org/8435731
________________________________
> Date: Mon, 28 Oct 2013 08:46:34 +1000
> Subject: Re: [Bitcoin-development] Advisory: PHP library Bitcoin SCI
> weak key generation
> From: gavinandresen@gmail.com
> To: a86551@outlook.com
> CC: bitcoin-development@lists.sourceforge.net
>
> Thanks for the warning; to be clear, "the Bitcoin SCI library" is this
> project?
> http://bitfreak.info/index.php?page=tools&t=bitsci
>
>
> On Mon, Oct 28, 2013 at 8:25 AM, Andres Home
> <a86551@outlook.com<mailto:a86551@outlook.com>> wrote:
> 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.
>
> --
> --
> Gavin Andresen
prev parent reply other threads:[~2013-10-27 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 22:25 [Bitcoin-development] Advisory: PHP library Bitcoin SCI weak key generation Andres Home
2013-10-27 22:46 ` Gavin Andresen
2013-10-27 22:48 ` Andres Home [this message]
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-W61AA4CD1C6C550B6166915820F0@phx.gbl \
--to=a86551@outlook.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/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