Google Chrome, Windows XP, Twitter SSL Certificate Problem

This is what many people running Google Chrome browser with Windows XP are getting when trying to connect to Twitter:

ChromeVsTwitter

There’s a “solution” going around to go to Settings, Show Advanced Settings, and then to check this:

ChromeNOFix

I tried that. It didn’t work.

Someone also suggested checking the Date and Time on the PC to see if it’s correct. Mine is, so that’s not it.

According to Google, the problem is that the new SSL Certificate from Twitter cannot be handled by Windows XP with Service Packs 1 or 2:

It looks like twitter.com’s SSL certificate was updated recently, and is valid from April 7, 2014 to May 9, 2016. If you are getting a certificate error for some websites only and you’re running Windows XP, then you most likely don’t have Service Pack 3.

It also looks like twitter.com is using a SHA-256 signed certificate, but SHA-256 wasn’t supported in XP until SP3. See http://support.microsoft.com/kb/322389

If you cannot load any HTTPS websites at all, then (1) ensure your computer’s year/date/time is correct, (2) if you have Kaspersky or ESET, disable “SSL scanning”, (3) if you are using Cisco ScanSafe, Cisco are working to fix it.

Well, I can’t load SP3 on my XP box. I tried it once and it slowed things to a crawl.

I can, however — at least so far! — get into Twitter using Firefox. But perhaps that might go away too when Firefox updates. Or maybe I’m stuck using the old and security-bleeding certificate. I don’t know.

It seems to me that people are going to have to get rid of Windows XP whether they want to or not.

This is why I sometimes rage against the tech world. This shouldn’t happen. Given the economic crisis that’s been ongoing since 2008, there are millions of people out there still running Windows XP because they have no other financial choice. Cutting them off from services they require is just cruel, if not actually discriminatory. Some kind of accommodation must made for them.

If there are further developments about this, I will update the post. In the meantime — at the time of this post — all of you stuck with this problem have a lot of company. See this Twitter Search.

Those of you with friends who can still get on Twitter, have them voice your misery to @Twitter, @Support, @jack (Jack Dorsey, who leads Twitter), and @GoogleChrome. Without a sense of how large this problem is, it won’t be addressed.

9 Comments

Filed under Google, Socialtech

9 responses to “Google Chrome, Windows XP, Twitter SSL Certificate Problem

  1. Mike, I take it you know Microsoft stopped supporting XP earlier this month. A gift for hackers; your machine may have been compromised. More info here: http://search.theregister.co.uk/?q=windows+xp

    • mikecane

      Yes. I know. I run scans regularly. But I expect the NSA has even backdoored the scanners too. I am mostly on a Win 7 notebook these days.

  2. Daniel Ortega

    Thanks a lot :D for posting a very good opinion about the problem. But, my own computer doesn’t have XP im working at a job that fills all of your predictions :/ and it’s sad that technology eats all that doesn’t have the standard

  3. Ish

    Thanks. This is very informative. It looks like we need to upgrade our OS to be able to browse our favorite sites.

  4. “I tried it once and it slowed things to a crawl.”
    It shouldn’t (at least anymore than XP SP2 does). Can you figure out what is happening?

  5. Also expect more sites to use SHA256 in the future.

  6. You are right… you are really right… they want to kill windows xp in all the possible way… xp, for me, is still one of the best OS did of all this time and I’m very disappointed of how they are trying to stop its life in order to encourage the migration to windows 8…

  7. I am also stuck with Windows XP Pro SP2 (Chrome version 37.0.2062.124, Official Build 281580).
    But here I found an odd solution to this problem. When Chrome blocks access and complains about SSL certificates, just type in “danger” and intro key … and it will let you access the site.
    I found the answer in this webpage (and in comments to the original password which used to be “proceed”, but now it is “danger”):

    http://www.pocketables.com/2014/02/override-chromes-new-ssl-error-connect-real.html
    https://productforums.google.com/forum/#!topic/chrome/5-Bf0o6YxgM%5B76-100-false%5D

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s