Tracy,

Point taken: "bad" is subjective.  I thought of using passwords, and then
thought of having to maintain group passwords and track potential violations
of that method.  I couldn't come up with a good way for the system to track
the violations for me (other than using a script to track what users moved
or logged onto what groups, and then scan that for violations), and didn't
want to do that task each day/week/month.  But the script that would do the
scanning would be using the logic I thought to apply to LOGONs and CHGROUP
commands, anyway.  As such, being subjective, I discounted it before making
my suggestion.  :)

I completely agree with you about firing a security violator.  In fact, I
think it's a great idea.  I also think that configuring your system to make
the security violation more difficult (or impossible) is best because then
we don't have to fire as many people.  (Recruiting and training being what
they are.)

But, just to play Devil's Advocate, however....

<snip>
Good vs. Bad are relative terms.
(Not as in Good vs. Evil, which are absolutes.)
<snip>

Um, no.  Good and Evil are both relative terms, as well.  Excluding possibly
zero degrees on the kelvin scale, there are no absolutes.

 ]:)      (evil smiley with horns)

Rs~

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *