nanog mailing list archives
Re: AOL fixing Microsoft default settings
From: chuck goolsbee <chucklist () forest net>
Date: Thu, 23 Oct 2003 21:47:28 -0700
How many other ISPs intend to follow AOL's practice and use their connection support software to fix the defaults on their customer's Windows computers?
Thankfully our focus is hosting & Colo, not access, so our pool is smaller and (theoretically) smarter. However this hasn't stopped us from doing similar things (such as disable/remove proxy server software) on client computers. Too many times I have called a client and asked "Why are you running a proxy server?" only to hear the reply "What's a proxy server?" (sigh)
I suppose I don't bother our clients with a clue, as their servers are already configured properly, and I am just protecting our clueless clients from themselves (or more accurately protecting my network from my clueless clients.)
Where it gets weird is when you take advantage of one privilege (like a software installer) to make other changes (disabling services) without permission. (I won't even touch the thick legal-ese of most EULA's which usually force the user to grant this permission beforehand)
Where does it stop being "helpful" and start being "harmful"?... As in Microsoft infamous disabling of competitor's products with their installers? Then the question becomes "who is being harmed?" I guess... the end-user or the competitor(s)?
Where I draw the line is the security of my own network, which granted is a pretty self-contained little world, unlike so may others here on NANOG.
On the other hand, I also have a .sig which is a quote from one of my staff, which illustrates another slippery factor of this particular slope...
--chuck goolsbee -- ______________________________________________________ There's only so much stupidity you can compensate for; there comes a point where you compensate for so much stupidity that it starts to cause problems for the people who actually think in a normal way. -Bill, digital.forest tech support
Current thread:
- AOL fixing Microsoft default settings Sean Donelan (Oct 23)
- Re: AOL fixing Microsoft default settings Jared Mauch (Oct 23)
- RE: AOL fixing Microsoft default settings Terry Baranski (Oct 23)
- RE: AOL fixing Microsoft default settings Brian Wallingford (Oct 23)
- Re: AOL fixing Microsoft default settings Chris Brenton (Oct 24)
- Re: AOL fixing Microsoft default settings Brian Bruns (Oct 24)
- RE: AOL fixing Microsoft default settings Terry Baranski (Oct 23)
- Re: AOL fixing Microsoft default settings Michael Loftis (Oct 23)
- Re: AOL fixing Microsoft default settings Christopher L. Morrow (Oct 23)
- Re: AOL fixing Microsoft default settings chuck goolsbee (Oct 23)
- RE: AOL fixing Microsoft default settings Brian Knoblauch (Oct 24)
- Message not available
- Re: AOL fixing Microsoft default settings Fred Baker (Oct 28)
- Re: AOL fixing Microsoft default settings Sean Donelan (Oct 28)
- Re: AOL fixing Microsoft default settings Henry Linneweh (Oct 28)
- Re: AOL fixing Microsoft default settings Daniel Golding (Oct 30)
- Re: AOL fixing Microsoft default settings Fred Baker (Oct 28)
- Re: AOL fixing Microsoft default settings Jared Mauch (Oct 23)
- <Possible follow-ups>
- Re: AOL fixing Microsoft default settings Stewart, William C (Bill), RTSLS (Oct 24)
- Re: AOL fixing Microsoft default settings Sean Donelan (Oct 24)
- Re: AOL fixing Microsoft default settings J Bacher (Oct 25)
- Re: AOL fixing Microsoft default settings Matthew Palmer (Oct 27)
- Message not available
- Re: AOL fixing Microsoft default settings Eric Kuhnke (Oct 25)
- Re: AOL fixing Microsoft default settings Sean Donelan (Oct 24)