Re:TinySSH is a small SSH server using NaCl, TweetNaCl
by edwintorok on Sunday May 11, 2014 @08:21AM
(#7728494)
I see 3 alternatives: use the original NaCl, use the unofficial fork libsodium, or use TweetNaCl.
The latter shares the same authors as the original NaCl, with the advantage of being much smaller.
I don't like the fact that TinySSH modified TweetNaCl, and added back MD5:
/*
Based on tweetnacl 20140427 (http://tweetnacl.cr.yp.to software.html)
- updated int/uint types to crypto_int/crypto_uint
- added crypto_stream_chacha20
- added crypto_hash_sha256
- added crypto_hash_md5
*/
I mean they use TweetNaCl because it has "state-of-the-art crypto", but then they add back MD5. Something is wrong here ...
Re:TinySSH is a small SSH server using NaCl, TweetNaCl
by luuse on Sunday May 11, 2014 @08:44AM
(#7728556)
Not sure why they added that back but the website states that
no older cryptographic primitives - rsa, dsa, classic diffie-hellman, md5, sha1, 3des, arcfour, ...
It is actually used in the code though. I didn't look into for what it was used though.
Re:TinySSH is a small SSH server using NaCl, TweetNaCl
by higherpurpose on Sunday May 11, 2014 @08:48AM
(#7728565)
That seems strange indeed. Some clarification is needed. Perhaps it's part of the whole NIST suite that's disabled right now?
Re:TinySSH is a small SSH server using NaCl, TweetNaCl
by edwintorok on Sunday May 11, 2014 @09:01AM
(#7728591)
It appears to be used only in tinysshd-printkey to print the key's fingerprint.
The fingerprint is 47 characters when printed, the key itself is 64. Since the key is so short does the fingerprint still server a useful purpose, or would it be enough to print only the key?
So, I don't see the problem here. If these guys had tried to cobble together a replacement for NaCl out of pieces like the curve25519-donna code, that would be a problem, because there's more potential to screw that up.