https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Patch Management and the bottom line

Bruce Schneier asks (rhetorically) why is it that Micro$oft can only bring itself to issue patches once a month to clean up security holes in its operating system, browser, and…

Bruce Schneier asks (rhetorically) why is it that Micro$oft can only bring itself to issue patches once a month to clean up security holes in its operating system, browser, and applications … but is willing to scramble within days to issue patches to its Digital Rights Management (DRM) software when someone out there finds a way to crack it?

The obvious (rhetorical) answer: money. Broken OS/browser/applications aren’t going to (yet) seriously impact the M$ bottom line. Causing media companies to think that their recordings aren’t safe, though, if they use the Micro$oft platform will. Thus the scramble to patch these gaps as soon as they come up.

It’s not that M$ is necessarily evil or wrong for this. But it’s indicative of where their true interests are (only peripherally with their end-user community), and who they’re willing to do what for to protect those interests.

20 view(s)  

Leave a Reply

Your email address will not be published. Required fields are marked *