>>Why this example ? Because it has following drawback: if the user leaves his terminal alone everyone could start each application under this "wrong" user id and password.
>>This company has decided to take this risk, that was a very surprising decision for me because they were extremly conservative, not to say paranoic about securitiy issues.
>
>PMFJI, but as I once said, we do that here, too, it makes a lot of things easier, but has the risk you mention. To beef up security, our LAN will soon strat enforcing a screen saver lockout for each user when away for more than a short time. Creates a slight additional effort for users, but it should tighten up security quite well, so seems like a reasonable solution...

Bruce,

don't appologize for jumping in, this is a reason of such a list ... have i told you something new ? :-)

you're solution with the screen saver is the same as on the my mainframe example. un can and should lock the "login screen" when leaving the desk, or it will be locked automatically after 15 minutes. same concept.