1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VaZ6X-0004KQ-RX
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 22:46:41 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.41 as permitted sender)
client-ip=74.125.82.41; envelope-from=gavinandresen@gmail.com;
helo=mail-wg0-f41.google.com;
Received: from mail-wg0-f41.google.com ([74.125.82.41])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VaZ6W-0000BO-S3
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 22:46:41 +0000
Received: by mail-wg0-f41.google.com with SMTP id b13so2772569wgh.4
for <bitcoin-development@lists.sourceforge.net>;
Sun, 27 Oct 2013 15:46:34 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.9.134 with SMTP id z6mr6617434wia.9.1382913994356; Sun,
27 Oct 2013 15:46:34 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Sun, 27 Oct 2013 15:46:34 -0700 (PDT)
In-Reply-To: <SNT151-W902926CDE9837FF83699C5820F0@phx.gbl>
References: <SNT151-W902926CDE9837FF83699C5820F0@phx.gbl>
Date: Mon, 28 Oct 2013 08:46:34 +1000
Message-ID: <CABsx9T2wnvxm2YYeXiatR5FMEESRZO+FKR45NFpaVerrPzJA+Q@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Andres Home <a86551@outlook.com>
Content-Type: multipart/alternative; boundary=001a11c2b1be637f6804e9c0c174
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bitfreak.info]
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VaZ6W-0000BO-S3
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Advisory: PHP library Bitcoin SCI weak
key generation
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 27 Oct 2013 22:46:42 -0000
--001a11c2b1be637f6804e9c0c174
Content-Type: text/plain; charset=ISO-8859-1
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> 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
--001a11c2b1be637f6804e9c0c174
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Thanks for the warning; to be clear, "the Bitcoi=
n SCI library" is this project?</div><div>=A0=A0<a href=3D"http://bitf=
reak.info/index.php?page=3Dtools&t=3Dbitsci">http://bitfreak.info/index=
.php?page=3Dtools&t=3Dbitsci</a></div>
<div><br></div><div><br></div><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">On Mon, Oct 28, 2013 at 8:25 AM, Andres Home <span dir=3D"ltr"><=
;<a href=3D"mailto:a86551@outlook.com" target=3D"_blank">a86551@outlook.com=
</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">For those developers who are using the Bitco=
in SCI library (maybe others too, I<br>
found two total and could only make contact with one), I would advise that =
you<br>
review how your software handles private key creation.</blockquote><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">--=A0<br></blockquote></div>--<br>Gavi=
n Andresen<br>
</div></div>
--001a11c2b1be637f6804e9c0c174--
|
