From: Pieter Wuille <pieter.wuille@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Who is creating non-DER signatures?
Date: Sun, 7 Apr 2013 18:21:00 +0200 [thread overview]
Message-ID: <20130407162059.GA19420@vps7135.xlshosting.net> (raw)
In-Reply-To: <CANEZrP3hu4C6-3gNFAcz85WL4HR+McHGiLG8E+-35VwyFGz7mw@mail.gmail.com>
On Sun, Apr 07, 2013 at 06:01:13PM +0200, Mike Hearn wrote:
> It'd help to know how the signatures are invalid.
The majority (~90%) is negative R or S values (which are just interpreted as
unsigned by OpenSSL, but if the top byte has its highest bit set, it must be
preceeded by a 0x00 accordinging to DER). A smaller number uses excessively
padded R or S value (with a 0x00 in front when it's not necessary). Finally
there are 4 signatures with an incorrect length marker in the beginning
(which likely means they contain some garbage at the end).
--
Pieter
next prev parent reply other threads:[~2013-04-07 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 15:34 Pieter Wuille
2013-04-07 16:01 ` Mike Hearn
2013-04-07 16:21 ` Pieter Wuille [this message]
2013-04-13 21:43 ` Pieter Wuille
2013-04-13 21:58 ` Gregory Maxwell
2013-04-15 11:51 ` Pieter Wuille
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=20130407162059.GA19420@vps7135.xlshosting.net \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(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