From: Drak <drak@zikula•org>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol Hash Comments
Date: Mon, 3 Mar 2014 12:39:36 +0000 [thread overview]
Message-ID: <CANAnSg2VsKaqPTckf45DemP0KxC05MZS++c7BP7MRL18f3YWzA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3owLtLnBHZ4vEBYcdkQ0WtpDDQ8CXK+92oNd1rgaEZyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
next prev parent reply other threads:[~2014-03-03 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 6:26 [Bitcoin-development] Positive and negative feedback on certificate validation errors Jeremy Spilman
2014-03-01 7:26 ` Wladimir
2014-03-01 7:50 ` Jeremy Spilman
2014-03-02 10:37 ` Mike Hearn
2014-03-02 7:52 ` [Bitcoin-development] Payment Protocol Hash Comments Jeremy Spilman
2014-03-02 8:44 ` Mike Hearn
2014-03-02 8:52 ` Drak
2014-03-02 10:39 ` Mike Hearn
2014-03-03 12:39 ` Drak [this message]
2014-03-02 18:18 ` [Bitcoin-development] Positive and negative feedback on certificate validation errors Troy Benjegerdes
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=CANAnSg2VsKaqPTckf45DemP0KxC05MZS++c7BP7MRL18f3YWzA@mail.gmail.com \
--to=drak@zikula$(echo .)org \
--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