Lately I’ve been getting a slough of notifications about how my browser and its obsolete ways will come crashing down from the heavens, relegated to the dust bin of history, on or around June 30th.
Just one problem with that. My browser isn’t out of date.
Seamonkey, the browser one might expect from ripping Firefox’s engine out and transplanting it into Netscape 7, might not be everyone’s cup of tea. It might not be used by enough to people to register as a browser to check. So that’s it, right? Weird browser equals outdated?
Maybe the websites check my user agent, which gives the following.
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3
Seamonkey TLS Settings
SeaMonkey 2.49.3 is the latest version of SeaMonkey, and Firefox 52 is still supported (until September) as an extended support release. Still, it may just not recognize SeaMonkey. That’s what I thought, until I looked into that date. I’m fairly confident I know what the issue is now.
On June 30th, the Payment Card Industry Data Security Standard will mandate that websites handling payment card data require TLS 1.1 or later. Good on them, but I’ve preempted that move by requiring secure websites I visit to support TLS 1.2. The websites ask my browser if it supports TLS 1.1. It responds negative. Must be outdated. Why bother asking if it supports TLS 1.2?
Alas, it seems some websites really are just asking my user agent.