phc-discussions - Re: [PHC] Argon2 code in C

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGiyFdcqY0GPEyVZLbCF1UQ+=2SWKqmoOG+xB8=dVCXwDZnoPA@mail.gmail.com>
Date: Tue, 06 Oct 2015 13:38:50 +0000
From: Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Argon2 code in C

Autoconf would just be for the build scripts of the reference code package.
The actual source code is independent of the build system and can be reused
as per the licence's terms.

On Tue, Oct 6, 2015 at 3:19 PM Jean-Pierre Münch <phc-jpm@...nch-ger.net>
wrote:

> Am 06.10.2015 um 12:33 schrieb Solar Designer:
> > On Tue, Oct 06, 2015 at 09:55:16AM +0000, Jean-Philippe Aumasson wrote:
> >> Any volunteer to create an autoconf script?
> > Not me, but: would this mean the code would then not build at all
> > without autoconf?  If so, that's a drawback that we should try to avoid.
> > Not every project that might want to embed an Argon2 implementation will
> > be autoconf'ed (nor will want to be).
> >
> > Alexander
> Just to give everyone an example of the above mentioned problem:
>
> I'm sure the Crypto++ project will strongly oppose requiring anything
> beyond standard libraries (including OpenMP) [1].
> So if the code forces other libraries to use AutoConf, this code can't
> be included in Crypto++ and we (= the Crypto++ team) have to code Argon2
> from scratch which I think is highly undesirable for all parties.
>
> [1]: https://cryptopp.com/wiki/External_Dependencies
>
> BR
>
> JPM
>

Content of type "text/html" skipped