5 ms·
What exactly is stopping Microsoft from issuing patches as soon as they're ready, and sysadmins configuring their machines to only look for said updates on the
by sarciszewski 12y ago
What exactly is stopping Microsoft from issuing patches as soon as they're ready, and sysadmins configuring their machines to only look for said updates on the second Tuesday of every month? This model works for other operating systems.
- CJefferson 12y agoBecause there are teams of people who jump on patches as soon as they are released, backward engineer what they fixed, and use that to produce attacks. Of course for bugs which already have public 0-day attacks, that isn't a problem, but the majority of bugs are not publicly known at fix time, and it is important that everyone gets the patches applied ASAP after release, hence the well-defined day when patches are released. At my work that day is purposefully blocked off to get patches applied, and be prepared for any fallout.
- sarciszewski 12y ago> Because there are teams of people who jump on patches as soon as they are released, backward engineer what they fixed, and use that to produce attacks. This should serve as an incentive to stay on the bleeding edge of security updates. Make automatic updates automatic without requiring a restart every time. Not an incentive to sit on our hands and wait until the second Tuesday of a month. The term Exploit Wednesday was coined in response to Patch Tuesday. :) Ultimately, I think this change from a monthly security release pattern to a "as soon as it's ready" security release pattern is what needs to happen. For the good of everyone. Then if people get 0wned, it's their own damn fault.