From: Pieter Wuille <pieter.wuille@gmail•com>
To: odinn.cyberguerrilla@riseup•net
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bug in key.cpp
Date: Tue, 6 May 2014 10:25:06 +0200 [thread overview]
Message-ID: <CAPg+sBj4e-rXxjda9=_q6R+wxUfufGnvLU0v=BmQ1+g742BMKA@mail.gmail.com> (raw)
In-Reply-To: <da34991a7a2db8f6f15401ed614cfe1e.squirrel@fulvetta.riseup.net>
On Tue, May 6, 2014 at 5:12 AM, <odinn.cyberguerrilla@riseup•net> wrote:
> You are right there is a bug in there.
>
> But the value is not 25% I think. Tinker some more. :-)
>
>>
>> Afaict, 3 is a perfectly valid value, meaning 25% of sig-> key recoveries
>> would fail erroneously...
Values 2 and 3 are only needed in theory. They together shouldn't
occur more than once in 2**127 (when the signature value is between
the group size and the field size).
That said, this is indeed a bug.
--
Pieter
prev parent reply other threads:[~2014-05-06 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 2:42 Srintuar
2014-05-06 3:12 ` odinn.cyberguerrilla
2014-05-06 8:25 ` Pieter Wuille [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='CAPg+sBj4e-rXxjda9=_q6R+wxUfufGnvLU0v=BmQ1+g742BMKA@mail.gmail.com' \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=odinn.cyberguerrilla@riseup$(echo .)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