3 ms·
This article contains no content except a decades-old rant against full disclosure. Two things to remember: the person who discovered the hole didn't put it th
by jrockway 16y ago
This article contains no content except a decades-old rant against full disclosure.
Two things to remember: the person who discovered the hole didn't put it there, nor is it likely he is the first person to see it. He is, however, the first person that was thoughtful enough to tell you about it so you could take mitigating action. The crackers wouldn't do that, nor would Microsoft.
As for the exploit code, well, he's a programmer. People don't believe you unless you prove it. He proved he was right by writing exploit code.
Bottom line: don't shoot the messenger. He is helping you! It's Microsoft that added a security hole to their product and hoped nobody would notice.
- fname 16y agoIt's Microsoft that added a security hole to their product and hoped nobody would notice This excerpt contains no content except a decades-old rant against how Microsoft doesn't care about security. I mean, really? It's unfortunate people still believe that Microsoft would add a security hole to their product and hope no one figured it out so they don't have to fix it.
- btilly 16y agoNobody thinks that Microsoft deliberately added this security hole. However once you find out about a hole like this in the wild,a natural response is to hope nobody finds out because you're busy and it is a hassle to try to fix it. And many, many companies, Microsoft included, have done exactly this. That's why the full disclosure movement arose in the first place. From remarks he has made, it seems that Tavis attempted to get them agree to a 60 day fix turn around. This is evidence that, in fact, Microsoft would have just sat on this bug report and hoped that nobody would notice.