16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

logind<br />

Options<br />

Note<br />

rlogind should always be invoked from inetd through the /etc/inetd.conf file.<br />

It should not be invoked from the shell. inetd sets up certain files and sockets<br />

needed by rlogind. Invoking rlogind directly gives unpredictable results.<br />

–a Specifies that the requester’s Internet address be checked against the local<br />

gethostbyname() file. This option has no effect because the rlogin program<br />

never uses the .rhosts file for authentication.<br />

–d Specifies that the debugging option be enabled. Informational messages on<br />

the rlogin process is written to the system log.<br />

–l Specifies that the .rhosts file for authentication not be used. This option<br />

has no effect because the rlogin program never uses the .rhosts file for<br />

authentication.<br />

–L Allows the calling of an ruserok exit that lives in /usr/sbin. A return code<br />

zero will allow bypassing of password checking. The installation is<br />

responsible for providing the ruserok exit.<br />

Note: IBM does not recommend using this capability. Using this capability<br />

may open security holes, allowing unauthorized users to access and<br />

modify files and MVS data sets. Even with the most rigorous<br />

checking in the ruserok exit, it is important to keep in mind the<br />

well-known IP spoofing attacks that make it impossible to accurately<br />

idenfity the remote user’s identity.<br />

IBM recommends that the -L flag not be specified. IBM will not<br />

accept APARS for security problems resulting from the use of this<br />

facility.<br />

When the -L flag is specified, /usr/sbin/ruserok is called, passing:<br />

v the name of the progrem, /usr/sbin/ruserok<br />

v ″hostname″ or ″hostname.domainname″ of the client<br />

v a superuser flag, an integer set to 1 if the user wants to be superuser<br />

v client user name, the username on the client system<br />

v server user name, the username on this (server’s) system<br />

If the ruserok program exits with a zero return value, the user is allowed to<br />

login. Otherwise, normal password checking will be done.<br />

Note: If the facility class is active, and the bpx.daemon is defined, then<br />

both inetd’s and rlogind’s usernames must be permitted to<br />

bpx.daemon and the ruserok program (as well as inetd and rlogind)<br />

must be marked program controlled.<br />

–m Specifies that multiprocessing support in the user’s address space be<br />

enabled. Using the –m option uses fewer system resources and provides<br />

faster performance for the end user.<br />

530 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference<br />

If you do not specify –m, each rlogin request causes two MVS address<br />

spaces to be consumed. The first address space is the rlogind code, which

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!