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: 
 <CAKmKYaDXs_L9LZkvcJLAkWhz=g05pdxMAHAo6XtkwLBQLkPSwg@mail.gmail.com>
Date: Wed, 6 Nov 2013 09:33:19 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <920A6185-FE9D-49ED-81AB-F481E432F738@apache.org>
References: 
 <CAKmKYaCPsh13vJE7pAJmF55pUOqvT7_=zYkJ6eJ1TzZ5TXtJkQ@mail.gmail.com>
 <F741C5AF-60A4-428D-8A34-94288C9090B3@apache.org>
 <CAKmKYaDvxEx_bX3==vuqLj6On9grm8US4FvAAQNz18Xds0bfBw@mail.gmail.com>
 <CAKmKYaDXs_L9LZkvcJLAkWhz=g05pdxMAHAo6XtkwLBQLkPSwg@mail.gmail.com>
To: dev List <dev@apr.apache.org>


On 6 Nov 2013, at 07:37, Dirkjan Ochtman wrote:

> On Wed, Oct 16, 2013 at 5:57 PM, Dirkjan Ochtman <djc@apache.org> wrote:
>> Well, the alternatives are (a) relying on an extra dependency for my
>> Apache module, probably NSS or OpenSSL or both, or (b) pulling in a
>> semi-random copy of SHA2 from the internet and including that. If APR
>> already included a maintained version of SHA2 (and it looks like it
>> already does, except it's not exposed to external users), that would
>> definitely make things easier for me.
> 
> Ping! Is this essentially of the table?

I had a brief look, and concluded it could rapidly lead to a lot of work.

An even briefer look just now in response to your ping suggests
I was missing your point, and that all you're asking for is that
random/unix/sha2.h be exposed in the public API.  Is that correct?

I would guess this code has never been tested, though there's
what looks like a placeholder in testpass.c.  Have you run it
at all?  How well does it work for you if you just copy sha2.h
manually to your APR include directory and use it for your module?

-- 
Nick Kew