Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <drak@zikula.org>) id 1WKSA7-0008Mi-SC for bitcoin-development@lists.sourceforge.net; Mon, 03 Mar 2014 12:40:03 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org designates 74.125.82.46 as permitted sender) client-ip=74.125.82.46; envelope-from=drak@zikula.org; helo=mail-wg0-f46.google.com; Received: from mail-wg0-f46.google.com ([74.125.82.46]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WKSA6-0003W5-K8 for bitcoin-development@lists.sourceforge.net; Mon, 03 Mar 2014 12:40:03 +0000 Received: by mail-wg0-f46.google.com with SMTP id z12so3149430wgg.29 for <bitcoin-development@lists.sourceforge.net>; Mon, 03 Mar 2014 04:39:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=KgcGbApa4aSzymTjspjXwWBOz4IJs8xzAitUDf2m1xo=; b=PJXWYk0QjUFdjwbuPB9kAHr84agf3xiudu7fnLxKRsoAgyJXm1CpXilVtUSBILnuSt W9DMtQ6FC9FK1422a4GWlixc9eCG7Jg74AWnCJyqqrQavYKIjAu3W+D6gw+aVl4MMG/L aMegVD1c6Wvfd2pk2AH2ahRQhGlhhizrIOQzOUGEDFLr+qebLrylGpJM4pgTLONuKm3y UtMwcnfkXVmPXyZJgCRSLt3G0r2y2MIvPAqGLqd+XEG8+q+fT1ipKE1A24qYOdbo86XG zKxAoW/bNAgKML94IlYlFBWZobgLQhFI3UtDGAtepiTgZZPuZ0yqIpYTURVEOo8adFzX CVhQ== X-Gm-Message-State: ALoCoQmceB9qqXv9cYZC8Ww5PMJfOXCMa7Z2f66S1VGSoUjJ0T1WK6DO+tib5cB0dhORUVQjL0WH X-Received: by 10.194.84.144 with SMTP id z16mr17440687wjy.23.1393850396482; Mon, 03 Mar 2014 04:39:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.205.69 with HTTP; Mon, 3 Mar 2014 04:39:36 -0800 (PST) In-Reply-To: <CANEZrP3owLtLnBHZ4vEBYcdkQ0WtpDDQ8CXK+92oNd1rgaEZyg@mail.gmail.com> References: <op.xb05iptvyldrnw@laptop-air> <op.xb2352ezyldrnw@laptop-air> <CANEZrP22SF4bD2pA3MyNmAojUmtZ20r=eL2Lgt=Fa4ZJyG=5SA@mail.gmail.com> <CANAnSg1fwkzXebbCMEf6XeGD0SG+ny=vKW-2nC_40yhkn1LVkg@mail.gmail.com> <CANEZrP3owLtLnBHZ4vEBYcdkQ0WtpDDQ8CXK+92oNd1rgaEZyg@mail.gmail.com> From: Drak <drak@zikula.org> Date: Mon, 3 Mar 2014 12:39:36 +0000 Message-ID: <CANAnSg2VsKaqPTckf45DemP0KxC05MZS++c7BP7MRL18f3YWzA@mail.gmail.com> To: Mike Hearn <mike@plan99.net> Content-Type: multipart/alternative; boundary=089e0102ddaec0b4bd04f3b31569 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WKSA6-0003W5-K8 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Payment Protocol Hash Comments 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: Mon, 03 Mar 2014 12:40:04 -0000 --089e0102ddaec0b4bd04f3b31569 Content-Type: text/plain; charset=UTF-8 On 2 March 2014 10:39, Mike Hearn <mike@plan99.net> wrote: > I'm just repeating the rationale Gavin gave me for adding this to the spec > last year when he was implementing it. Perhaps it only applied to some > versions of PHP or something like that. > OK, but certainly now, SHA-2 is available as standard in PHP and has been since PHP 5.1.2 as part of the hash() function. You can see from usage stats that means practically every installation http://w3techs.com/technologies/details/pl-php/5/all is PHP 5.2 and above. Unless there is some other compelling reason, I would suggest removing SHA-1 from the specification. Drak --089e0102ddaec0b4bd04f3b31569 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2= March 2014 10:39, Mike Hearn <span dir=3D"ltr"><<a href=3D"mailto:mike@= plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrote:<br><blo= ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left= -width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi= ng-left:1ex"> <div dir=3D"ltr">I'm just repeating the rationale Gavin gave me for add= ing this to the spec last year when he was implementing it. Perhaps it only= applied to some versions of PHP or something like that.</div></blockquote> <div><br></div><div>OK, but certainly now, SHA-2 is available as standard i= n PHP and has been since PHP 5.1.2 as part of the hash() function. You can = see from usage stats that means practically every installation <a href=3D"h= ttp://w3techs.com/technologies/details/pl-php/5/all">http://w3techs.com/tec= hnologies/details/pl-php/5/all</a> is PHP 5.2 and above.</div> <div><br></div><div>Unless there is some other compelling reason, I would s= uggest removing SHA-1 from the specification.</div><div>=C2=A0</div><div>Dr= ak</div></div></div></div> --089e0102ddaec0b4bd04f3b31569--