TLS 1.0 and 1.1 deprecation.

General project discussion.
Use this as a last resort if your topic does not fit in any of the other boards but it still on-topic.
Forum rules
This General Discussion board is meant for topics that are still relevant to Pale Moon, web browsers, browser tech, UXP applications, and related, but don't have a more fitting board available.

Please stick to the relevance of this forum here, which focuses on everything around the Pale Moon project and its user community. "Random" subjects don't belong here, and should be posted in the Off-Topic board.
New Tobin Paradigm

Re: TLS 1.0 and 1.1 deprecation.

Post by New Tobin Paradigm » 2020-01-11, 14:27

What's your point?

User avatar
therube
Board Warrior
Board Warrior
Posts: 1760
Joined: 2018-06-08, 17:02

Re: TLS 1.0 and 1.1 deprecation.

Post by therube » 2020-01-11, 14:44

Point is, if some cares to test their browser, they can fire up those links & see how things behave, currently, or may behave, in the future.

User avatar
Moonchild
Project founder
Project founder
Posts: 38968
Joined: 2011-08-28, 17:27
Location: Sweden

Re: TLS 1.0 and 1.1 deprecation.

Post by Moonchild » 2020-01-11, 16:47

Legacy Cryptography (Moderate Risk)
If your browser connects to one of these sites, your web traffic is probably safe from attackers in the near future. However, your connections to some sites might not be using the strongest possible security. Your browser may use these settings in order to connect to some older sites.
Subdomain Result Secure Result?
tls-v1-0 connected 🆗 OKAY
tls-v1-1 connected 🆗 OKAY
cbc connected 🆗 OKAY
3des cannot connect ✅ YES
dh2048 cannot connect ✅ YES
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 5794
Joined: 2015-12-09, 15:45

Re: TLS 1.0 and 1.1 deprecation.

Post by moonbat » 2020-01-12, 03:14

Moonchild wrote:
2019-10-03, 11:30
I honestly don't get it. these warnings should be sent to server administrators as part of evangelism; what good is it to bother browser users with it?
Maybe they (Google/Mozilla) want to force the issue by breaking support for it in the browser so that website operators are compelled to change when their users are inconvenienced.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
KDE Neon on a Slimbook Excalibur (Ryzen 7 8845HS, 64 GB RAM)
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Jabber: moonbat@hot-chili.net

User avatar
Isengrim
Board Warrior
Board Warrior
Posts: 1324
Joined: 2015-09-08, 22:54
Location: 127.0.0.1

Re: TLS 1.0 and 1.1 deprecation.

Post by Isengrim » 2020-01-12, 03:30

moonbat wrote:
2020-01-12, 03:14
Maybe they (Google/Mozilla) want to force the issue by breaking support for it in the browser so that website operators are compelled to change when their users are inconvenienced.
This was my thought as well. Make it look like a problem with the site and users will complain about the site rather than the browser.
a.k.a. Ascrod
Linux Mint 19.3 Cinnamon (64-bit), Debian Bullseye (64-bit), Windows 7 (64-bit)
"As long as there is someone who will appreciate the work involved in the creation, the effort is time well spent." ~ Tetsuzou Kamadani, Cave Story