Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:Unimplementable (Score 1) 332

It depends on how we define "transparent". If you set up the cron job yourself then it's not really transparent. Strictly speaking, I don't think Apple is suggesting that they will secretly set up silent background updates without providing an opt-in as well as history reporting either.

Comment Missing A Key Reason (Score 1) 256

All this reasoning misses a key point. If Microsoft releases patches on a very frequent basis, IT departments aren't necessarily going to patch their infrastructures (remember we're talking potentially about tens or even hundreds of thousands of nodes) with the same cadence. So in many cases those infrastructures are going to lag behind the current patch level.

But once a patch is made available, it provides an opportunity to reverse engineer the patch to determine what the defect was. This gives hackers the opportunity to devise attacks that leverage the vulnerability.

So you see what happens: if Microsoft releases too frequently it creates a large window of opportunity for infrastructures to remain unpatched and therefore vulnerable to exploits.

Microsoft chose a monthly release strategy as a balance between too often and not often enough. It's not perfect but the alternative is far less desirable.

Help! I'm trapped in a PDP 11/70!

Working...