From: slush <slush@centrum•cz>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Python implementation of RFC 6979
Date: Tue, 10 Sep 2013 18:52:26 +0200 [thread overview]
Message-ID: <CAJna-HiZb3BOm0emdiw6QU1sMVV3GXt33fPBJ73S2MRgQtbs+w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1331 bytes --]
reply other threads:[~2013-09-10 16:59 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=CAJna-HiZb3BOm0emdiw6QU1sMVV3GXt33fPBJ73S2MRgQtbs+w@mail.gmail.com \
--to=slush@centrum$(echo .)cz \
--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