Originally posted by: Nothinman
This patch was out for a month and yet still banks and government agencies were still affected. This indicates the places were we would assume the highest amount of security measures would be used realy failed to even follow fundamental aspects of computer security. So they would be screwed irregardless which OS they use.
Consider how difficult it is to keep all the companie's workstations up to date. You can't let them just use WU because for a company of any size that would kill your Internet connection periodically as 500+ machines try to download patches from WU. You can probably use AD GPOs to push updates, but most places are still in the beginning to middle of their AD migration if one is happening at all. And I believe MS SUS requires AD and only works on servers currently, which makes it borderline useless. With a host of Linux boxes it would be simple to write a script to scp an RPM over and install it remotely.
There is no way for you to just download the patch to a ftp server on your lan or anything like that?
It that is true, what a crappy way to distribute patches. I guess that could be another example of bad design choices. Lets make it the most expensive and inconvenent way possible to distribute patches! We will put it on a single server(or server group) on the internet and not make it accessable in any other way!! We can make it easy, but it will co$t..
I know from my experiances with Macs (helping run 180+ G4s on a school LAN), that we kept up to date on patches. The main administrator would keep track of the updates issued from Apple and e-mail or call me whenever we had a new update. If it was a big one like a quicktime upgrade I'd just go to versiontracker.com and download it from a file server. Then just systematicly go to all of them and install the package. If it was up to me I'd figure out a Unix way of doing it, but they (bosses) were all Windows and Old-school mac people and that scared them and made me do it one by one. Small patches I would install just by running the update program and download them directly from apple.
To mitigate any problems the Mac guru would just install the updates on her personal computer and make sure that it didn't cause anyproblems. The only thing we would put off for a while the OS upgrades, like from 10.2.4 to 10.2.6 and stuff like that. We were carefull because the W2k file servers were have a hissy fit and refused to work properly with the macs. At firsty we thought it was the OS updates because it seemed to coincide with 10.2.4 upgrade. however it turned out the w2k reverse lookup configuration was screwed up and combined with networking issues were the main problems. Go figure.
Once we got the liscence for the remote desktop I installed the clients on a all the Macs and the server stuff I descreatly installed on a few key machines. Once that was installed I could simply download the patches from versiontracker and apple.com. Then I would use the remote desktop to broadcast the patches to 50 or so computers at a time and they would automaticly install the updates. If I was carefull with which ones required reboots I could install them on computers that were even being used at the time by students and they wouldn't notice the difference. Me, a part time temp, would single handedly install all the nessicary patches and updates in a couple hours of work for a entire lab of macs. (cover a hundred macs in two rooms, while still hepling out students and teachers with different problems or questions, and people running in and out working for a half hour on a random mac for some project or homework.)
So I guess OS X just spoiled me.
Linux would be even easier cause then I would have ssh set up before hand on the client desktops to accept a automated script using scp to download and install the relevent packages. (probably simple tarballs)