4 ms·
Honestly, this sounds like a terrible decision. Preventing bad decisions by ensuring that no dev ever needs to set the cipher order in the first place would be
by jeroenhd 5y ago
Honestly, this sounds like a terrible decision. Preventing bad decisions by ensuring that no dev ever needs to set the cipher order in the first place would be a good idea, but ignoring flags and removing developer control because Google Knows Best is a terrible idea.
- deleted 5y ago[deleted]
- slownews45 5y agoSounds like game over for google. That said, there is trend even outside of google to move away from high levels of configurability in these sort of security sensitive areas. I'd be curious what a system like wireguard lets you do in terms of bit twiddling. OpenSSL was sort of famous for letting your turn just about every knob you wanted. Not sure that was a ton better. And I have heard some concern that folks like apple put so much into attack surface on things like imessage (memoji's?) for messages from unknown and untrusted users (ie, new users you aren't texting with can send entire set of stuff imessage supports which is a TON vs just being text only to start). So even in other areas dialing down things might be helpful.
- jeroenhd 5y agoI agree with Google that applications shouldn't normally be setting these parameters manually and I agree with their chosen defaults, but if developers are going through the effort of setting these values they're clearly doing it for a reason. That reason could be "the API doesn't allow developers to easily access the defaults" but the fix for that would be something completely different. Even in OpenSSL you don't get that much choice in TLS 1.3 because the number of usable ciphers and key exchange methods has been severely reduced.
- tssva 5y ago"I'd be curious what a system like wireguard lets you do in terms of bit twiddling." WireGuard doesn't allow you to do anything in terms of bit twiddling. This is one of the claimed benefits of WireGuard over OpenVPN or IPsec.
- tptacek 5y agoTo pile on: WireGuard doesn't even have ciphersuites, exactly because of the arguments Filippo makes in this post. You get Curve25519 and ChaPoly, and that's it.
- slownews45 5y agoIs it clear that then that as OP says this is a terrible idea? It seems then in keeping with ideas being followed elsewhere. Casually (not a security expert) this makes a let of sense to me. If I'm copying my stack overflow code out for my security stuff, maybe have fewer footguns? Not sure this is a terrible idea then.
- Ajef 5y agoIt's open source. If you are capable of making such decisions on encryption with founded confidence you can also vendor the library and adapt it. The reality is most developers (almost every developer I know) won't spend particularly much time on deciding settings for encryption - and honestly if they spent 10x the amount they did doing research they would still only base their opinions on things they find online like blog posts (not mathematics or government whitepapers). I don't believe the approach is bad. It doesn't take the ability away from you to choose. It just adds a hurdle (vendoring the library), which imo stops a lot of bad decisions from overconfident developers. [edit]: typo
- deleted 5y ago[deleted]