I'd be exposing additional elements of the OpenSSL API via additions to the
commons crypto API. Since I wouldn't be adding any additional
dependencies, I would expect that licensing and portability would remain
unchanged. Would it not?
Thanks,
Alex
On Sat, Feb 27, 2021 at 1:08 PM Gilles Sadows
Le sam. 27 févr. 2021 à 19:00, Bernd Eckenfels
a écrit :
>
> Hello,
>
> I don’t think it’s a Good idea to introduce native dependencies to formerly
> pure Java projects.
+1
[I thought that the idea was a (pure) Java implementation.]
> So i think native optimized hash implementations would fit b
Hello,
I don’t think it’s a Good idea to introduce native dependencies to formerly
pure Java projects. So i think native optimized hash implementations would fit
better in commons-crypto. So I would say go for it, keep in mind license
clearance and portability.
Gruß
Bernd
--
https://Bernd.eck
See also
https://commons.apache.org/proper/commons-codec/apidocs/org/apache/commons/codec/digest/DigestUtils.html
Gary
On Sat, Feb 27, 2021, 09:58 Gilles Sadowski wrote:
> Hi.
>
> Le sam. 27 févr. 2021 à 15:51, Alex Remily a
> écrit :
> >
> > I'm working on a project that makes heavy use of h
Hi.
Le sam. 27 févr. 2021 à 15:51, Alex Remily a écrit :
>
> I'm working on a project that makes heavy use of hashing, and I'd like to
> use the OpenSSL implementation. Thoughts on adding support for the SHA-2
http://commons.apache.org/proper/commons-codec/apidocs/org/apache/commons/codec/diges
I'm working on a project that makes heavy use of hashing, and I'd like to
use the OpenSSL implementation. Thoughts on adding support for the SHA-2
and/or Blake2 family into commons crypto? I'm happy to do the work if
there's someone out there willing to review and advise.
Alex
