4 ms·

Apps shouldn't let users enter OpenSSL cipher-suite strings

• stop50 1y ago
  Clientside apps: definitly not on Server side: i usually set an minimum tls version, The ciphers baseline of HIGH and removing some ciphers like sha1, CBC and any NULL Containing cipher
• tatersolid 1y ago
  “Safari can’t open the page because it couldn’t establish a secure connection to the server.” Irony or satire?
  • LoganDark 1y ago
    Satirony?
  • faeranne 1y ago
    Not even curl can connect... seems whatever this is on about isn't important enough for them to let people even try to read.
• userbinator 1y ago
  Yes they should. Enough with this authoritarian user-hostile attitude. I can't even connect to your site as you reject my ClientHello, and I'm not going to figure out why.
  • h2782 1y ago
    "Those who can't do it teach it."
• jsnider3 1y ago
  I'm not going to take security advice from someone whose website I can't open in https.
• dontdoxxme 1y ago
  https://web.archive.org/web/20250606081030/https://00f.net/2025/06/06/cipher-suites/ https://web.archive.org/web/20250606081030/https://00f.net/2... given this seems to not accept (most?) TLS handshakes...
• xena 1y ago
  Does not load in Firefox
• tbrownaw 1y ago
  Site won't load so I can't see if it's advocating no choices or a different mechanism or granularity for choices. But, say, itsec banning some tls1.2 "for compatibility reasons" options is less drastic than itsec just banning tls1.2 from the company network entirely.
• finnigja 1y ago
  ruh roh... "no secure protocols supported", per https://www.ssllabs.com/ssltest/analyze.html?d=00f.net https://www.ssllabs.com/ssltest/analyze.html?d=00f.net
• rurban 1y ago
  That's how I implemented it. Just with less checkboxes.