And with VM:Secure, you can accomplish the same effect by using the Rules
Facility. With the following rules, the actual password is immaterial:
REJECT * LOGON
ACCEPT userx LOGONBY
With the LBYONLY method, you are more restricted in the number of users who can
have LOGONBY privileges, but, considering the ids you listed, that is unlikely
to be a consideration.
If someone else has the ability to reset passwords for users, you need to take
steps to guard the LBYONLY passwords of the machines of interest.
Regards,
Richard Schuh
> -----Original Message-----
> From: The IBM z/VM Operating System
> [mailto:[email protected]] On Behalf Of Hans Rempel
> Sent: Tuesday, March 03, 2009 3:58 PM
> To: [email protected]
> Subject: Re: Using LBYONLY
>
> LOGONBY or LBYONLY as special passwords as is NOLOG. If you
> use LOGONBY or LBYONLY as the password and have LOGONBY
> statement specifying userx then you can logon as follows:
>
> LOGON OSASF By userx
>
> And when prompted you must supply userx's password.
>
> Hans
>
> -----Original Message-----
> From: The IBM z/VM Operating System
> [mailto:[email protected]] On Behalf Of Wandschneider, Scott
> Sent: March 3, 2009 6:36 PM
> To: [email protected]
> Subject: Using LBYONLY
>
>
> Can some tell me if LBYONLY can be used as a password, with
> an appropriate LOGONBY statement for OSASF, OSAMAINT,
> OSADMIN1, OSADMIN2, and OSADMIN3
> *and* the GUI interface?
>
> Thanks in Advance,
> Scott R Wandschneider
>
> Senior Systems Programmer|| Infocrossing, a Wipro Company ||
> 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ':
> 402.963.8905 || Ë:847.849.7223 ||
> :: [email protected] **Think Green - Please print
> responsibly**
>
>
> Confidentiality Note: This e-mail, including any attachment
> to it, may contain material that is confidential,
> proprietary, privileged and/or "Protected Health
> Information," within the meaning of the regulations under the
> Health Insurance Portability & Accountability Act as amended.
> If it is not clear that you are the intended recipient, you
> are hereby notified that you have received this transmittal
> in error, and any review, dissemination, distribution or
> copying of this e-mail, including any attachment to it, is
> strictly prohibited. If you have received this e-mail in
> error, please immediately return it to the sender and delete
> it from your system. Thank you.
>
