IE zero-day Fix
-
What's IE? Just kidding. By the way if users don't use IE and wait for normal W8.1.1 updates are they vulnerable still?
-
@technobabble said:
What's IE? Just kidding. By the way if users don't use IE and wait for normal W8.1.1 updates are they vulnerable still?
It affected all IE versions, including 11.
-
Ouch. Glad I'm all FF and Chrome.
-
IE required at one client because Toyota refuses to update their legacy systems to use modern web standards.
Not only IE required but the a 11 page (mostly screenshots) PDF of instructions on how to change settings in IE in order to use it with their portal.It is horrible to deal with.
-
Toyota. Denying secure IE just like they denied that their cars wouldn't stop correctly.
-
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
-
88% of my PCs are reporting as patched as of today. I am going to update the other 12% tonight via PDQ Deploy
-
@tfl said:
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
Good Guy Microsoft Meme in the works?
-
@Bill-Kindle said:
@technobabble said:
What's IE? Just kidding. By the way if users don't use IE and wait for normal W8.1.1 updates are they vulnerable still?
It affected all IE versions, including 11.
I got that @Bill-Kindle, but I wanted to know if they don't use IE are they still vulnerable? Many of my clients are residential or break/fix business clients and most don't use IE.
-
@technobabble said:
@Bill-Kindle said:
@technobabble said:
What's IE? Just kidding. By the way if users don't use IE and wait for normal W8.1.1 updates are they vulnerable still?
It affected all IE versions, including 11.
I got that @Bill-Kindle, but I wanted to know if they don't use IE are they still vulnerable? Many of my clients are residential or break/fix business clients and most don't use IE.
The risk is IE specific as I understand it.
-
Good to know...working on blog/newsletter stuff this weekend and wanted to be current and correct!
-
-
@tfl said:
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
That's a terrible precedent to set. Now XP users are going to want more patches the next time something happens.
-
@alexntg said:
@tfl said:
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
That's a terrible precedent to set. Now XP users are going to want more patches the next time something happens.
Wasn't the patch to IE, not to XP though? If not, then I agree.
-
@scottalanmiller said:
@alexntg said:
@tfl said:
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
That's a terrible precedent to set. Now XP users are going to want more patches the next time something happens.
Wasn't the patch to IE, not to XP though? If not, then I agree.
To my knowledge it was only IE, not XP. The versions of IE affected were predominate on XP though, which I why I think a lot of people are getting it confused thinking it's an XP update when it's not.
-
@Bill-Kindle said:
@scottalanmiller said:
@alexntg said:
@tfl said:
@Dashrender said:
Hold the phone.. XP's listed in there.
Indeed - this is most generous of Microsoft.
Sets an interesting precedent for the future but I think they did the good thing here!
That's a terrible precedent to set. Now XP users are going to want more patches the next time something happens.
Wasn't the patch to IE, not to XP though? If not, then I agree.
To my knowledge it was only IE, not XP. The versions of IE affected were predominate on XP though, which I why I think a lot of people are getting it confused thinking it's an XP update when it's not.
I wouldn't call it predominate. It affected all versions from IE 6 - 11. So three of those versions are on XP (6-8, 3 of them), but the rest all all available on Windows 7 (8-11, 4 of them).
I was really hoping MS wasn't going to provide an IE fix for XP, but perhaps the code was identical for XP's version of IE 8 as it was for Windows 7's version of IE 8. If this is the case, XP will continue to get IE patches until 2020 when Windows 7 is force ably retired.
-
One would hop that they would only not provide new patches. Not actively block them from the platform. I would expect MS Office to keep getting update. For example.
-
@scottalanmiller said:
One would hop that they would only not provide new patches. Not actively block them from the platform. I would expect MS Office to keep getting update. For example.
Office? I guess you mean Office 2007 or newer since Office 2003 was EOL'ed with XP. To that end, I agree, Office 2007 updates should definitely run on XP or there should be hell to pay. But since you can't get support for XP any longer I could see MS saying - if it doesn't work, we're sorry we can't help you until you are on a supported base platform as XP is no longer considered a supported platform for Office 2007 or 2010.
