3 ms·
That so many vendors have collaborated to synchronize a patch release is interesting Hacker News. The odd quasi-disclosure -- here's how to test, here's a mostl
by gojomo 18y ago
That so many vendors have collaborated to synchronize a patch release is interesting Hacker News. The odd quasi-disclosure -- here's how to test, here's a mostly-helpful patch, but full details will wait a month or until third parties figure it out -- is Hacker News.
Regular reminders of the general insecurity of DNS are also a public service, attached to megapatch firedrills or not.
- tptacek 18y agoIt would be news if it was (a) news or (b) really true. Regarding (a), there was more collaboration and a bigger fire drill on the OULU.FI SNMP findings from 2003. That was a series of memory corruption and code execution findings in multiple different implementations. ---------------------------------------------------------- EVERYTHING BELOW THIS LINE WAS WRONG Also, Microsoft patches on a schedule ("Patch Tuesday"), so if you have an activist security researcher trying to keep details from getting out, the major coordination problem is already solved: you're releasing on Patch Tuesday. What I'm saying is, if you find ANYTHING, and you want to talk about a mass vendor reaction, get Microsoft on board and you're done. Dan has a professional relationship with Microsoft. Regarding (b), most of the implementations that are patching fall into two categories: (1) --- Derivatives of ISC BIND (2) --- Fantastically weak embedded or proprietary DNS implementations that were totally screwed prior to any new research result, and are now catching up on 13-15 years of DNS best practices for fear of being found out.