Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!H.CS.CMU.EDU!Rudy.Nedved
From: Rudy.Nedved@H.CS.CMU.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Security or what?
Message-ID: <1987.4.8.20.39.14.Rudy.Nedved@h.cs.cmu.edu>
Date: Wed, 8-Apr-87 15:52:16 EST
Article-I.D.: h.1987.4.8.20.39.14.Rudy.Nedved
Posted: Wed Apr  8 15:52:16 1987
Date-Received: Sat, 11-Apr-87 08:57:16 EST
References: <8704072114.AA02584@emptys.cc.umich.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26
Approved: tcp-ip@sri-nic.arpa

Michael,

I read your message in response to Mark Cripin's flame. I only want
to comment on guru versus system programmer misunderstanding you have.

We have many people at CMU that can crack a system but are impossible to
communicate with. These people are brilliant but their personaility is very
very poor on interpersonal skills. In many cases, they are in control of
important software. There is no intent to discourage such situations by
management since all benefit....on the other hand they are not policy or
decision makers except in their own "world". 

In some cases, I have dealt with people that control software and blantantly
ignore management. Management is in a position of needing them and not
feeling the issue is critical enough to fire (since they have a hard time
evaluating the situation). The result is the hacker is viewed as a guru
who controls the systems and runs it as he sees fit and management tolerates
him until he leaves.

In the final analysis, hacker is not the same as guru which is not the
same as system programmer which is not the same as system manager. Luckily,
many people have some or all of these "jobs" at the same time....makes
life interesting.

Cheers,
-Rudy