Am 26.09.2014 um 15:41 schrieb Christopher Myers:
All true, and good points :) I wasn't thinking so much specifically regarding this particular bash bug, but the broader issue of patches in general (heartbleed, et al.)
I'd considered going with 11.4 evergreen when I did the server build, but at the time couldn't get it to work on my box for whatever reason; it would make it about halfway through booting off of the media (dvd|network|flash all the same) and then the box would totally freeze regardless of what fixes I attempted from Google, what hardware was/wasn't installed, etc., so I had to do 12.2 (which worked fine.) I've done a ton of customization to the box and have it running very sweetly now, and don't have a compelling reason to upgrade it to the new evergreen.
It is mostly secured away from the nastier parts of the internet, so most patches aren't really necessary on it, but I was just curious what others were doing when they were in situations similar to mine.
Honestly? I would build the required patches in OBS for myself. I started that back in 11.1 and let other's get it as well and ooops, it was called Evergreen. But actually. Not sure what the nastier parts of the Internet are. So it is a case by case decision. If you cannot fix it yourself and cannot make sure to avoid the possibility in the first place you are in trouble and really should update. At some point you'll have the pain anyway. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org