0patching a 0-day: Windows gdi32.dll memory disclosure

Re:0patching a 0-day: Windows gdi32.dll memory disclosure by Declanomous on Thursday March 02, 2017 @02:11PM (#13777202)

I would just choose a different software provider at that point. Though I suppose that could be fairly effective at getting enterprise users who are stubbornly holding on to a particular version of software to move on. Like my IT director for example, who sent a long rambling email to everyone about how horrible it was for all of us that Microsoft was leaving us out to dry by not supporting IE6.

For the record this was in April 2014, after Heartbleed was disclosed. IE6 had a 4% market share at the time, so yeah.

[ Parent | on HN ]

Re:0patching a 0-day: Windows gdi32.dll memory disclosure by hermitdev on Thursday March 02, 2017 @08:39PM (#13780093)

Wow, if I worked for a company that was still on, at latest, Windows XP and Windows Server 2003 in 2014, I think I'd be looking for a different job.

Even my tech-illiterate father, who has a laptop with XP on it, knows enough to not even connect to the internet with it anymore. He mostly uses it to play solitaire currently, and uses a newer laptop w/ Win10 for anything on the internet.

(edit: grammar)

[ Parent | on HN ]

Re:0patching a 0-day: Windows gdi32.dll memory disclosure by Declanomous on Friday March 03, 2017 @02:44PM (#13785660)

I am looking for a different job, and it's largely in part due to issues with the IT situation. I basically have stuck around this long because while the IT situation is Kafkaesque, I've really liked a lot of other aspects of the job, and it was in a field I feel strongly about.

[ Parent | on HN ]