Hi

You have made several assumptions without any fact, and I am confused at that. One, I am not an any "mess" at all. I'm not sure why you would say that. I actually have a great job, and enjoy what I do. Our network runs perfectly, is secure, and I get to work with talented people. Further, you allude to Tim Mullen being my "friend" a couple of times. I'm not sure why you would say that either. I have seen Mr. Mullen speak before, but I have never met him, and he is not my friend.

Something else that confuses me about your post is that you go from "stupidest thing I ever read" to "stupidest thing ever written". If that is the case, then you must not read much, if at all.

Your post shows an elite, assumptive, condescending, and insulting (the "slop" comment) so I think I made a mistake in thinking I was replying to a professional. Not to be insulting, but you kind of sound like one of those "GRC" newsgroup people.

But, let's get to your analogy, as I think you are way off base with it. Many security people, SANS for instance, would take your example and say that if running the M-Class in full-time four wheel drive all the time made it burn oil and made the wheels wear incorrectly, then Mercedes should not give the driver the capability of running it full time. It would be Mercedes fault for letting them do it. At the very least, they should be warned by a flashing light saying "do not do this."
Besides- you don't even make the right conclusion- it does not have anything to do with your "duty" or "perceptive" ability to tell the drive not to drive full time in four wheel drive because that in an expected use of the vehicle. You gave them that option, and they are using it. There is nothing perceptive about your noticing burned oil and worn wheels. That is your job, just like an MCSE.

The difference is that mechanics (MCSE's) do not tell drivers not to speed, they don't tell them not to drive drunk, and don't tell them not to drive off a cliff without a seatbelt. That is the difference.

Hope that helps.

Thanks.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/166/20411#20411