Hacker News Reader

Maybe I'm raving mad but doesn't 60 days seem like forever? That's tons of time for anyone to write, test and release their exploit. What takes 60 days, unless you've screwed up something completely fundamental to how your software works (in which case you'd spend far more than 60 days anyway)?

View on HN

A company like Microsoft only releases new software rarely - e.g. in Microsoft cases, patches are bundled once a month. If you report a bug just before the bundle comes out, their earlier possible [1] response is ~35 days, anyway.

[1] Of course, "possible" depends on how much pressure you put on them, which is the whole argument of the Full-Disclosure camp...

Testing the patch.

And middle management meetings.

and sometimes it takes a while to understand the true nature of a bug.

and sometimes the "right way" to fix something is unclear.

and sometimes the fix straddles multiple components, managed by different teams.

and sometimes "that guy" who knows the subsystem is off at Disneyland for two weeks.

60 days can pass very quickly, especially as the project and vulnerability complexity grows. It's a short enough window to put the vendor under time pressures from day one.

Reply on news.ycombinator.com