4 ms·
Maybe they are and this was already documented internally, but potentially marked as a low threat, but now that it was found outside of Microsoft it's a bigger
by ToastyMallows 12y ago
Maybe they are and this was already documented internally, but potentially marked as a low threat, but now that it was found outside of Microsoft it's a bigger problem? I'm just spitballing here, one would have to assume that Microsoft is doing static code analysis.
- pbhjpbhj 12y agoOK, but it wasn't found before the current OS cycle presumably because one would imagine they'd fix it ... ha-ha! So it either wasn't found or they found it and continued to bake it in to the OS nonetheless. Which is better?