4 ms·
The problem for this falls directly on vendors that make their crap hard to keep up to date. I'm not blaming Microsoft for this, as they're actually pretty dec
by zdw 15y ago
The problem for this falls directly on vendors that make their crap hard to keep up to date. I'm not blaming Microsoft for this, as they're actually pretty decent - the problem usually is with 3rd parties that don't validate on the newest releases.
Seriously people - there's a reason OS vendors have prerelease software programs. If you're not testing your software on say the Windows 8 beta or on prerelease versions of OS X 10.7.3, then when it doesn't work on day one of release it's likely your fault, not the OS vendor for breaking stuff.
The larger issue is that software testing is a PITA... this is probably a shared issue between Dev and Ops. Every time I see a new single function "installs software X outside of package management" program, I have to think that both sides are doing the other a disservice. Dev's should be able to get their software on multiple platforms easily, and Ops shouldn't have to wrestle to get it installed. We've only been wrestling with this problem for the last 30 years...
- cr4zy 15y agoI wouldn't say Microsoft is pretty good at updates. I once installed a patch for a security flaw in DNS in our Windows DNS server and got reamed by my boss for bringing our site down. I have found the policy of installing all updates when first setting up a Windows server and then never touching it again to work quite well. We also keep all non-HTTP access to a VPN. Alternatively, don't use Windows. App Engine is my preferred platform for new projects and the security on that is most likely top notch and constantly upgraded.
- fakeempire 15y ago"I have found the policy of installing all updates when first setting up a Windows server and then never touching it again to work quite well." I think you need to reevaluate your policies immediately. Not applying security patching isn't a good policy.
- nobody314159265 15y agoYou have a choice between: The chance of someone bothering to hack you multiplied by the chance that the new patch doesn't include several new security bugs Or the chance of a new untested patch bringing down your business.
- mkchandler 15y agoThis is why we use QA servers for most of our systems. We try our best to test all functionality on a patched QA server before deploying patches to our production servers. We have had good success doing this (with Windows at least.)
- nobody314159265 15y agoSo leaving your main system exposed to the new zero day vunerability for a whole day while you do the tests!
- briandear 15y agoThe real question is why anyone would willingly run a windows server for anything?
- DanBC 15y agoNo. You wait a few hours (maybe half a day) and see how other people get on with the patch. Then you patch. Or you leave more holes for the automated bots and worms to exploit.