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 Sadowski <gillese...@gmail.com> wrote: > Le sam. 27 févr. 2021 à 19:00, Bernd Eckenfels > <e...@zusammenkunft.net> 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 better in > commons-crypto. So I would say go for it, keep in mind license clearance > and portability. > > > > Gruß > > Bernd > > > > > [...] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
