by jsnider3 on 6/10/25, 4:23 AM
I'm not going to take security advice from someone whose website I can't open in https.
by stop50 on 6/6/25, 8:51 AM
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
by dontdoxxme on 6/10/25, 4:25 AM
by tbrownaw on 6/10/25, 4:38 AM
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.
by finnigja on 6/10/25, 5:15 AM
by userbinator on 6/10/25, 4:09 AM
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.
by rurban on 6/10/25, 5:23 AM
That's how I implemented it. Just with less checkboxes.
by tatersolid on 6/10/25, 4:10 AM
“Safari can’t open the page because it couldn’t establish a secure connection to the server.”
Irony or satire?
by xena on 6/10/25, 4:27 AM
Does not load in Firefox