4 ms·
Agreed. It's also super weird to have designed a new protocol that supports multiple cipher suites, it's very well established through the design of SSL and SSH
by RL_Quine 4y ago
Agreed. It's also super weird to have designed a new protocol that supports multiple cipher suites, it's very well established through the design of SSL and SSH now that there is absolutely no place for cipher negotiation in protocols.
- api 4y agoYeah, right now any new protocol should pick either ChaCha if you want to be fast on general purpose hardware and/or be hipster certified or AES (256) if you want to be fast on AES accelerated hardware and/or be FIPS(ter?) certified. I can't think of a single reason to pick anything else right now or to support negotiation.
- RL_Quine 4y agoThe reason negotiation is in this product is that the underlying code is actually from 2008, which explains why the cipher selection exists in the protocol, as well as the inclusion of TwoFish.