Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.44 as permitted sender)
	client-ip=209.85.219.44; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f44.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CAPg+sBhYuK79Gost2p1ksytNUTjAHz1REC1DRQaP2UD=cjRA0g@mail.gmail.com>
References: <CAPg+sBhYuK79Gost2p1ksytNUTjAHz1REC1DRQaP2UD=cjRA0g@mail.gmail.com>
Date: Sun, 7 Apr 2013 18:01:13 +0200
Message-ID: <CANEZrP3hu4C6-3gNFAcz85WL4HR+McHGiLG8E+-35VwyFGz7mw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0444e925fbecf804d9c76d1c
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Who is creating non-DER signatures?
Precedence: list

--f46d0444e925fbecf804d9c76d1c
Content-Type: text/plain; charset=UTF-8

It'd help to know how the signatures are invalid.


On Sun, Apr 7, 2013 at 5:34 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:

> (cross-post from bitcointalk.org)
>
> Hello all,
>
> as some may know, Bitcoin uses DER-encoded signatures in its transactions.
> However, OpenSSL (which is used to verify them) accepts more than just the
> strict DER specification (it allows negative numbers, extra zero padding,
> extra bytes at the end, and perhaps more). As we don't like the de-facto
> specification of the Bitcoin block validity rules to depend on OpenSSL,
> we're trying to introduce a rule to make such non-standard signatures
> invalid. Obviously, that can't be done as long as any significant amount of
> clients on the network is creating these.
>
> I've monitored all transactions the past weeks (1.4M transactions), and it
> seems 9641 of them contain at least one non-standard signature. See
> https://bitcointalk.org/index.php?topic=169620.0 for a list of the top
> addresses that had coins used as inputs in such transactions. If you
> recognize any of these addresses, or have an idea of who owns them or what
> software they are using, please let me know.
>
> Thanks!
>
> --
> Pieter
>
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

--f46d0444e925fbecf804d9c76d1c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It&#39;d help to know how the signatures are invalid.</div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Apr =
7, 2013 at 5:34 PM, Pieter Wuille <span dir=3D"ltr">&lt;<a href=3D"mailto:p=
ieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>(cross-post from <a hr=
ef=3D"http://bitcointalk.org" target=3D"_blank">bitcointalk.org</a>)</div><=
div><br>
</div>Hello all,<div><br></div><div><div>as some may know, Bitcoin uses DER=
-encoded signatures in its transactions. However, OpenSSL (which is used to=
 verify them) accepts more than just the strict DER specification (it allow=
s negative numbers, extra zero padding, extra bytes at the end, and perhaps=
 more). As we don&#39;t like the de-facto specification of the Bitcoin bloc=
k validity rules to depend on OpenSSL, we&#39;re trying to introduce a rule=
 to make such non-standard signatures invalid. Obviously, that can&#39;t be=
 done as long as any significant amount of clients on the network is creati=
ng these.<br>

</div><div><br></div><div>I&#39;ve monitored all transactions the past week=
s (1.4M transactions), and it seems 9641 of them contain at least one non-s=
tandard signature. See=C2=A0<a href=3D"https://bitcointalk.org/index.php?to=
pic=3D169620.0" target=3D"_blank">https://bitcointalk.org/index.php?topic=
=3D169620.0</a>=C2=A0for a list of the top addresses that had coins used as=
 inputs in such transactions. If you recognize any of these addresses, or h=
ave an idea of who owns them or what software they are using, please let me=
 know.</div>

<div><br></div><div>Thanks!</div></div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div><br></div><div>--=C2=A0</div><div>Pieter</div><div><br></=
div></font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
Minimize network downtime and maximize team effectiveness.<br>
Reduce network management and security costs.Learn how to hire<br>
the most talented Cisco Certified professionals. Visit the<br>
Employer Resources Portal<br>
<a href=3D"http://www.cisco.com/web/learning/employer_resources/index.html"=
 target=3D"_blank">http://www.cisco.com/web/learning/employer_resources/ind=
ex.html</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--f46d0444e925fbecf804d9c76d1c--