3 ms·
I'm interested in knowing if this affects Windows XP. From the page: > Other versions or editions are either past their support life cycle or are not affected
by codys 12y ago
I'm interested in knowing if this affects Windows XP. From the page:
> Other versions or editions are either past their support life cycle or are not affected
And XP is unlisted. Seems to imply that it could be either one.
- yuhong 12y agoWell, Server 2003 is very similar to WinXP and I think http://support.microsoft.com/kb/894199 http://support.microsoft.com/kb/894199 lists a WEPOS/POSReady 2009 version.
- ams6110 12y agoXP is not supported. Why would they make a statement one way or the other?
- hueving 12y agoTo face the reality that there are a ton of XP deployments. It would be in Microsoft's interest to at least notify them of the problem and even incentivize them to upgrade.
- tracker1 12y agoWell, XP likely has the same issues in their implementation, given similar origins, especially for older protocols. XP requires SP3 for TLS1 iirc, and doesn't support > TLS 1.0, let alone 1.1 or 1.2 (current). There are other issues with browsers (namely that a lot of XP users are still using IE8, which has a host of other issues). The project I am now on isn't supporting IE8, we're going to load some HTML5/ES6 shims, and a notice to users that it may not work, but given how poorly MS's VMs for testing IE8 on XP are, it's really a non-starter. IE8 is about 3-4% of our current traffic, which will likely be displaced by mobile traffic once our site/app is no longer mobile hostile. I wouldn't consider XP a viable OS at this point, and many users would be better off with a more recent ubuntu, and wine.