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
116
117
118
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1VJRHx-0006a7-LP
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Sep 2013 16:59:41 +0000
X-ACL-Warn:
Received: from mail-vb0-f44.google.com ([209.85.212.44])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VJRHw-0001uZ-CO
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Sep 2013 16:59:41 +0000
Received: by mail-vb0-f44.google.com with SMTP id e13so5157143vbg.17
for <bitcoin-development@lists.sourceforge.net>;
Tue, 10 Sep 2013 09:59:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
:to:content-type;
bh=j3/36w+Q2rKkJD6KzMbAiaF+BdLPsdavd2F3qjxekCo=;
b=ChdMXXD0lgBWKT8o+c5txABmIN8AKAiJoClzjjSXtDQ46P3zCBUxcCrv6vX61srCVD
rXldvE0EQIKDL4OtmWNYQUcxy6HAmOb17Koqfg7vZOmNlLr1EWFVL6+bUm9x1rGF2kvn
Ppi1hjOfp9NFyFwqmOA4w9/yv3sAyKvgZgQG4Os1FmxL7j7l1vhamoTQI9xC8STX5WTi
xFz5cKMqDK7WbSkyrgE6cHyWPGOWzrgbYaO40GUCBOXWXE9mMRVOfEgwUlPT2U3L1fWO
kF21k2SI5WE00bh1I3aAxUU9UqhlV8c+hhi91INeAWWY0As/TlCIZLidzDbiG8zbkEL1
pV3Q==
X-Gm-Message-State: ALoCoQn5GHOs+qOV7lDVJJuK1PxI47G+gUto9UkQcUfw3g0/P4cHmz3dmt5QkLTuB+5qCXkVunYR
X-Received: by 10.58.198.13 with SMTP id iy13mr23703188vec.11.1378831976714;
Tue, 10 Sep 2013 09:52:56 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.235.136 with HTTP; Tue, 10 Sep 2013 09:52:26 -0700 (PDT)
From: slush <slush@centrum.cz>
Date: Tue, 10 Sep 2013 18:52:26 +0200
X-Google-Sender-Auth: cikEYwkpP6VDDBha5OtmNP3GUx8
Message-ID: <CAJna-HiZb3BOm0emdiw6QU1sMVV3GXt33fPBJ73S2MRgQtbs+w@mail.gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b6dcb7c2d681304e60a56e6
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VJRHw-0001uZ-CO
Subject: [Bitcoin-development] Python implementation of RFC 6979
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: Tue, 10 Sep 2013 16:59:41 -0000
--047d7b6dcb7c2d681304e60a56e6
Content-Type: text/plain; charset=ISO-8859-1
Hi all,
yesterday I found some time and implemented RFC 6979 into python-ecdsa
module.
RFC 6979 proposes algorithm of calculating 'k' value for signature from
private key and signed data, so the 'k' is unique, but deterministic for
every signature. This enabled simple unit tests of code using ECDSA
signatures as well as some nice use cases for blackbox testing of 3rd party
software (you can calculate on your own if some software is making valid
signature, because there's no randomnes involved in the process). Yes, I'm
referring Trezor :-).
There's my fork of python-ecdsa with RFC 6979:
https://github.com/trezor/python-ecdsa/
There's pull request waiting for python-ecdsa author aproval:
https://github.com/warner/python-ecdsa/pull/10
Aaand there's RFC 6979: tools.ietf.org/html/rfc6979
Thanks,
slush
--047d7b6dcb7c2d681304e60a56e6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi all,<div><br></div><div style>yesterday I found some ti=
me and implemented RFC 6979 into python-ecdsa module.</div><div style><br><=
/div><div style>RFC 6979 proposes algorithm of calculating 'k' valu=
e for signature from private key and signed data, so the 'k' is uni=
que, but deterministic for every signature. This enabled simple unit tests =
of code using ECDSA signatures as well as some nice use cases for blackbox =
testing of 3rd party software (you can calculate on your own if some softwa=
re is making valid signature, because there's no randomnes involved in =
the process). Yes, I'm referring Trezor :-).</div>
<div style><br></div><div style><div>There's my fork of python-ecdsa wi=
th RFC 6979:</div><div><a href=3D"https://github.com/trezor/python-ecdsa/">=
https://github.com/trezor/python-ecdsa/</a></div><div><br></div></div><div =
style>
There's pull request waiting for python-ecdsa author aproval:=A0<a href=
=3D"https://github.com/warner/python-ecdsa/pull/10">https://github.com/warn=
er/python-ecdsa/pull/10</a></div><div style><br></div><div style>Aaand ther=
e's RFC 6979:=A0<a href=3D"http://tools.ietf.org/html/rfc6979">tools.ie=
tf.org/html/rfc6979</a></div>
<div style><br></div><div style>Thanks,</div><div style>slush</div><div sty=
le><br></div><div style><br></div></div>
--047d7b6dcb7c2d681304e60a56e6--
|
