Jon
Jon
bash, so I think your pull request should have fixed it.
If/when you do feel you can use libsodium, that also opens up two things which could be useful: - scrypt as a PBKDF. This should be (much) less vulnerable to...
@ThomasWaldmann That sounds less fragile than the current implementation at least (I think). The secretbox option from libsodium, despite the larger nonce, adds the same 40 byte overhead to the...
https://www.imperialviolet.org/2014/02/27/tlssymmetriccrypto.html < not a perfect comparison (it's ChaCha20, not XSalsa20, but I believe the performance is supposed to be similar), and that's one or more intel processor generations ago, but...
Seems unlikely aes-ctr will be added in libsodium from how that thread has evolved. I think I agree with the why, too. The nice thing about libsodium is it inherits...
Though it does complicate a migration to different algorithms without adding more dependencies
***several months elapse\*** One snag in implementing this easily is the expiry time which was added. With e.g. `JSON.dump`, this is serialised to something like `"2014-08-15 14:46:26 UTC"` and then...
Thanks for submitting this! Have a few questions and comments: What are the implications of this change? Will it change user visible behaviour (e.g. how values get round-tripped through the...
:+1: I almost implemented this when I wrote the fixes to the crypto, but in the end, didn't have the time.
Hi there! Thanks for the patch What Rubocop settings did you use for this?