Win XP / Twitter issue

We have one remaining Win XP desktop that we hoped to use for running a couple of specialist applications until May or early June. The OS is fully patched and other software is up to date. As of yesterday (10th April) we found ourselvees unable to access aany Twitter page via Chrome or Opera. An SSL error is reported as follows:

�The site uses SSL, but Google Chrome has detected either high-risk insecure content on the page or problems with the site's certificate. Do not enter sensitive information on this page. Invalid certificate or other serious https issues could indicate that someone is attempting to tamper with your connection to the site.�

Devices on the same network (computers running later Windows operating systems and our Android tablets) all access Twitter without a hitch.

Is this Twitter�s response to the end of Microsoft support for XP, the Heart Bleed bug, or what...?

Alphonso and Jess

EDIT: Twitter updated its certificate on 8th but we could access pages until 10th.

Edited by deleted (Fri 11-Apr-14 02:47:06)

Are all the machines you are compaing running the same version of Chrome? It is possible that the XP machine has a different version that has different checking. It certainly sounds more like a Chrome issue to me than a Twitter or XP issue.

Have you tried accessing Twitter from a different browser on the XP machine (IE or Firefox)?

Is the time and date on the PC correct?

Yes.

All computers are using the same version of Chrome- it's the latest issue. One Android tablet is a Kindle using the Silk browser...not sure about A's Nexus. The XP computer cannot access any Twitter page using Chrome or Opera...so it can't just be Chrome. We seldom use IE on the XP machine because we can't use the latest issue but I've tested it whilst posting about this issue and it won't display any Twitter page either. There's no Twitter problem with any other device and this is our only (known) web issue using the XP PC. I'm inclined to think it's as Twitter/XP problem perhaps in response to Heartbeat SSL issues but neither of us are qualified to know. I doubt we'll wait another month before replacing this system. Meanwhile, all ideas welcome

Jess

Maybe it was MS's parting shot for their last patch Tuesday? Has the XP machine done any Windows updates in the last 24 hours? You could also try doing a system restore to the last time it worked to see if that fixes it - would show if it is an update to Windows that has caused the problem (just remember that you might lose other things doing the system restore).

That seems a probable answer, Ian. I downloaded the last XP patches on 8th or 9th. Even if it was the 9th the issue didn't appear immediately or perhaps we just didn't access Twitter via the XP system until 10th. I don't think I'll opt for a restore. I've never found it a good solution except for the most minor issues. We'll be looking for a replacement in the next few days.

Many thanks for your interest and input

Jess

Maybe it's something to do with Heart bleed and twitter revoking a certificate?

(Complete guess)

Alphonso, Windows XP with automatic updates is supposed to automatically update certificate stores on the Windows XP platform so that Windows XP keeps up to date with the latest SSL technologies and SSL certificate providers. I would suspect that this is now no longer supported and as such you get the nag warning. I hope this is of some assistance.

I'm also running XP all patched, but I dont have any issues with twitter using firefox.

I would check your anti virus software, as it's odd that 2 web browsers (Chrome and Opera) will give exactly the same pop up message.