Re: [dev] securiy guidance

From: Michael Forney <mforney_AT_mforney.org>
Date: Tue, 6 Mar 2018 15:23:33 -0800

On 2018-03-06, petern_AT_riseup.net <petern_AT_riseup.net> wrote:
> On 2018-03-06 10:01, Truls Becken wrote:
>> Some libraries to look at are; libressl, libtomcrypt, nacl.cr.yp.to,
>> libsodium, nettle, libgcrypt and libmcrypt.
>
> Hello Truls,
>
> thank you for this list. I was hoping there would be a publicly
> available algo that could be inlined in the source since I really only
> need 1 algorithm, not a whole suite.
>
> If sticking to libraries, is there any one you recommend most?
> Preferably non-GPL.

Another related project I've been following is https://monocypher.org/

It has a quite permissive license and encourages inlining the source
like you want.
Received on Wed Mar 07 2018 - 00:23:33 CET

This archive was generated by hypermail 2.3.0 : Wed Mar 07 2018 - 00:36:08 CET