5 ms·
"WireOver uses what we believe are the most appropriate, safe, up-to-date, peer-reviewed crypto primitives, implementations, and parameters [...] Fingerprint Al
by ctz 13y ago
"WireOver uses what we believe are the most appropriate, safe, up-to-date, peer-reviewed crypto primitives, implementations, and parameters [...] Fingerprint Algorithm: MD5"
I fear this page was written with a straight face :(
- deleted 13y ago[deleted]
- tashmahalic 13y agoThere's a tradeoff between collision resistance and fingerprint string length. We chose MD5 because people are comfortable with it in ssh, it's a shorter string to verify than something like SHA-256, and because we planned to make your peer's entire public key base64 available if you really wanted to go that extra mile (currently not available). What would you prefer personally: (1) MD5 fingerprint for convenience AND entire peer public key base64 available if you really want; vs (2) just a longer SHA-256 fingerprint.
- pjscott 13y agoIf you just want a shorter string, I'd prefer truncated SHA-256.
- tptacek 13y agoYes, this is the correct way to get a shorter hash. Using MD5 is a terrible idea.
- tashmahalic 13y agoWe're changing it.
- tptacek 13y agoGood call.
- adam-f 13y agoI'm confused by their claim of hashing and THEN salting authentication codes. On the server-side, we don't store the authentication code in plaintext. We hash it with PBKDF2 / SHA-256, salt it, then store it.
- tashmahalic 13y agoIt's a salted hash. That page is corrected, thanks.