Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: SHA2 in APR
From: Nick Kew <niq@apache.org>
In-Reply-To: <20131106235756.2591b73d@hub>
Date: Thu, 7 Nov 2013 10:24:15 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <E8247B52-C252-4CF8-888C-DFDFBA6BF27C@apache.org>
References: 
 <CAKmKYaCPsh13vJE7pAJmF55pUOqvT7_=zYkJ6eJ1TzZ5TXtJkQ@mail.gmail.com>
 <F741C5AF-60A4-428D-8A34-94288C9090B3@apache.org>
 <20131106235756.2591b73d@hub>
To: dev List <dev@apr.apache.org>


On 7 Nov 2013, at 05:57, William A. Rowe Jr. wrote:

>   Otherwise, it seems prudent to get out of
> the hashing business and rip out md/sha1 entirely from apr 2.

-1 to ripping: that's pulling the rug from under existing apps.
At worst, deprecate.

The question is about exposing existing sha2 code.
For: it's there, and serves someone's need.
Against: it would appear to be less than complete, and to need a
fair bit of work to look comprehensive.

I guess I should take yours as a vote against what I was mulling over:
namely inviting Dirkjan to submit a patch and commit if it WorksForMe
and noone shouts?

> I have no issue with providing a simple hash, these are used for just
> about all arbitrary string values where you need to uniquify them into
> a predictable byte token.

That sounds like existing apr_md5 apps.

-- 
Nick Kew