markdascher

3 ms·

1. 1.▲
   by markdascher 4y ago

   It's a good idea, and some sort of easily-verified compatibility with openssl was actually an early goal. But I gave up on that since the algorithms are so different. A compatible mode would end up sharing very little code, so it would
2. 2.▲
   by markdascher 4y ago

   I haven't yet. This was my path to Frama-C: 1. Try writing C code that's "obviously safe." Gave up on that pretty quickly. 2. Maybe if I make all buffers global, I can verify some basics with a script. Gave up when I lea
3. 3.▲
   by markdascher 4y ago

   You're right. The honest answer is that my nose has been in this for so long that I've lost track of what's interesting and what isn't. =) A big reason to mention quantum safety is just to make it an explicit goal. If I&
4. 4.▲
   by markdascher 4y ago

   > Why 12288 bytes for p0? Good question! Tripling the first block's size (12288=3x4096) happened the most recent commit, to make all of the Padmé sizes possible. https://codeberg.org/markdascher/moochacha/c
5. 5.▲
   by markdascher 4y ago

   This started out as an excuse to try writing C code safely. Eventually stumbled upon Frama-C, which is amazing. But anyway, moochacha is a simple file encryption command based on libsodium's Argon2id, BLAKE2b, and ChaCha20-Poly1305. No
6. 6.▲
   Show HN: Moochacha, quantum-safe file encryption (analyzed by Frama-C)(codeberg.org)

   75 points by markdascher 4y ago|24 comments