On 2018-03-07 00:23, Michael Forney wrote:
> 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.
Hi Michael,
thanks, this looks really nice and small. I'm doing my homework reading
crypto
On 2018-03-06 9:01 am, Truls Becken wrote:
Some libraries to look at are; libressl, libtomcrypt, nacl.cr.yp.to,
libsodium, nettle, libgcrypt and libmcrypt.
Has anyone here seen or mentioned bearssl? [https://bearssl.org/] It
looks like it meshes with the suckless philosophy quite effectively.
On 2018-03-06 9:09 am, harry666t wrote:
So yes, the entire password store should be kept in one encrypted file
and so it can be opened and closed.
And then merges become a total pain. You might as well use Keepass.
I don't see why this must be so. Just decrypt the password store, merge,
and
pet...@riseup.net wrote:
I have to yet read up if it is safe to use
with a single key, i.e. encrypting n passwords with the same secret
key.
Make sure to use salting in this case. Otherwise using the same password
for multiple sites/keys would be visible.
You also want to hide the keys them
On 2018-03-08 06:57, Markus Teich wrote:
> pet...@riseup.net wrote:
>> I have to yet read up if it is safe to use
>> with a single key, i.e. encrypting n passwords with the same secret key.
>
> Make sure to use salting in this case. Otherwise using the same
> password for multiple sites/keys would
