Windows 10 0day exploit goes wild, and so do Microsoft marketers

Re:Windows 10 0day exploit goes wild, and so do Microsoft ma... by becarefulyo on Monday February 06, 2017 @10:35AM (#13580351)

Disclosure: I work at MS but not on the kernel or anything related to this security bug. Opinions are my own.

I've seen one-line bug fixes introduce many other bugs.

Adding a null check is always suspicious. Is the system in an invalid state? Should it fail fast instead of swallowing the error?

Maybe the code wasn't touched in several years. Maybe the person that wrote it no longer works there. Maybe the code in question doesn't have good test coverage or documentation. There are so many variables to consider when assessing risk of code changes.

[ Parent | on HN ]

Re:Windows 10 0day exploit goes wild, and so do Microsoft ma... by tremon on Monday February 06, 2017 @11:06AM (#13580704)

Maybe the person that wrote it no longer works there. Maybe the code in question doesn't have good test coverage or documentation

These are not valid excuses for a company the size of Microsoft.

[ Parent | on HN ]

Re:Windows 10 0day exploit goes wild, and so do Microsoft ma... by Sunset on Monday February 06, 2017 @11:23AM (#13580937)

These are the kind of consideration only companies the size of Microsoft are likely to have.

[ Parent | on HN ]

Re:Windows 10 0day exploit goes wild, and so do Microsoft ma... by Relys on Monday February 06, 2017 @05:58PM (#13585130)

Touché!

[ Parent | on HN ]