Cryptographic Right Answers

Re:Cryptographic Right Answers by loup-vaillant on Tuesday April 03, 2018 @06:37PM (#16750051)

Take Monocypher or TweetNaCL, and rip off any primitive you don't need. This may be enough. Even when you take the whole thing, Monocypher only needs 30kb of x86-64 machine code when compiled with -Os. If you only keep authenticated encryption and x25519, which are enough for many uses, I think you should be able to halve that down to 15kb or less.

If speed doesn't matter, TweetNaCl is even smaller.

If those aren't enough still, you may want to dive in, learn a ton about crypto (starting with https://www.crypto101.io/), and investigate the sponge construction, whose versatility may allow you to shrink the code even more. Perhaps. I'm in over my head at this point.

[ Parent | on HN ]

Re:Cryptographic Right Answers by posterboy on Tuesday April 03, 2018 @10:55PM (#16751513)

avr has aes extensions, surely arm cortex-m has similar. are those any good, are they used by the libs you mention?

[ Parent | on HN ]

Re:Cryptographic Right Answers by tptacek on Wednesday April 04, 2018 @07:41PM (#16760396)

Neither of those libraries uses any extensions. TweetNaCl is a famously minimal implementation of NaCl in portable C by the NaCl authors. Monocypher is a library 'loup-vaillant wrote as a sort of side project. TweetNaCl does see some use, but libsodium is the most popular NaCl implementation, and libsodium's author provides his own low-footprint misuse-resistant crypto API separately.

Neither TweetNaCl nor 'loup-vaillant's library really addresses the low-footprint concern.

[ Parent | on HN ]

Re:Cryptographic Right Answers by loup-vaillant on Wednesday April 04, 2018 @01:57AM (#16752341)

If they have hardware AES support, forget everything I said. Monocypher and TweetNacl are portable C, they don't use extensions of any kind.

[ Parent | on HN ]