Mark writes:
> I've seen some companies that use Security/3000 without MPE passwords.  I
> never liked this solution.

With SAFE you can assign MPE passwords to users, accounts, and groups, and
if SAFE isn't active (you just rebooted and haven't started it yet, etc.)
then that security will be in effect by default.  Once you start SAFE up,
the MPE passwords are deactivated and replaced by SAFE's own password
system.  So the fallback MPE passwords are always there, but users should
never need to know that they're there or what they are.  One logon, one
password.

> In issues of security, multiple layers are good.  This statement is not
> contradiction to what Gavin is saying as I'm sure he would agree that that
> it is better to have multiple barriers.  I'm sure the SAFE system does not
> store its password in a manner that allows it to be retrieved like MPE.

Of course, they're one-way encrypted.

G. "plugging away on an early Saturday morning"

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