should TLS 1.0 still be enabled - by default?

therube: any website that still requires it?

I thought Google had delivered capital punishment to sites still using such old cryptosuites

oh, don't know. just asking in general, because in SeaMonkey, 1.0 is enabled by default.

good question then

1.0 enabled, 1.1 & 1.2 is a "grayed" state, 1.3 enabled

For websites I don't think so. Might be some private devices around needed it. If you should still use them is another question? :) Turned off 1.0 and 1.1 for a long time now.

that's wg9s's latest. (don't know offhand about current SM beta)

then should defaults be changed for 2.53.15 release ?

same. Same codebase minus some work in programm stuff plus a few prefs aiding debugging.

I'm sure your average enterprise appliance doesn't even do anything but clear HTTP, but maybe, somewhere in a trillion-dollar corporation there must be some old appliance that demands TLS 1.0

i guess i meant to say, 2.53.14 (where 2.53.14b1 /is/ the same way)

Unless the sky is falling I am not altering prefs for 2.53.14. Not sure about IanN

news.ycombinator.com/item?id=32809126 the sky will fall the day Hackernews recognize there is life beyond Chrome

therube and all if you have some time please test the next 2.53.15b1 pre. Added about 400 patches for media, webrtc and images over the weekend till now. Hopefully stable :)

glad too - once i get the chance to restart SeaMonkey. as it is, can't at the moment. (haven't been able to since, 11:31:47 AM 08/15/2022)

anyhow, disabled 1.0 & 1.1 on my end.

I omitted Bug 1453127 which caused some crashes the last time with at least one streaming site. Stupid me just didn't add it to the notes which one. Might add it again later now that basically all prerequiste stuff is in.