Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ruserok(3) [osf1 man page]

ruserok(3)						     Library Functions Manual							ruserok(3)

NAME
ruserok - Allows servers to authenticate clients LIBRARY
Standard C Library (libc.a) SYNOPSIS
#include <unistd.h> int ruserok ( char *host, int root_user, char *remote_user, char *local_user ); PARAMETERS
Specifies the name of a remote host. Specifies a value to indicate whether the effective user ID of the calling process is that of a root user. A value of 0 (zero) indicates the process does not have a root user ID. A value of 1 indicates that the process has local root user privileges, and the /etc/host.equiv file is not checked. Points to a username that is valid at the remote host. Any valid username can be specified. Points to a username that is valid at the local host. Any valid username can be specified. DESCRIPTION
The ruserok() (remote command user OK) function allows servers to authenticate clients requesting services. The hostname must be specified. If the local domain and remote domain are the same, specifying the domain parts is optional. To determine the domain of the host, use the gethostname() function. The ruserok() function checks for this host in the /etc/host.equiv file. Then, if necessary, the subroutine checks a file in the user's home directory at the server called $HOME/.rhosts for a host and remote user ID. RETURN VALUES
The ruserok() function returns 0 (zero) if the subroutine successfully locates the name specified by the host parameter in the /etc/hosts.equiv file or if the IDs specified by the host and remote_user parameters are found in the $HOME/.rhosts file. If the name specified by the host parameter was not found, the ruserok() function returns a value of -1. FILES
Contains service names. Specifies foreign hostnames. Specifies the remote users of a local user account. RELATED INFORMATION
Functions: gethostname(2), rcmd(3), rresvport(3), sethostname(2) Commands: rlogind(8), rshd(8) delim off ruserok(3)

Check Out this Related Man Page

HOSTS.EQUIV(5)						      BSD File Formats Manual						    HOSTS.EQUIV(5)

NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8), rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1). Each line of these files has the format: hostname [username] The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from which only the host names are checked), or a ``+'' wildcard (allow all hosts). The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a ``+'' wildcard (allow all remote users). If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user may login with the same user name. EXAMPLES
somehost A common usage: users on somehost may login to the local host as the same user name. somehost username The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same user name. +@anetgroup username The user username may login to the local host from any machine listed in the netgroup anetgroup. + + + Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv). WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity. Therefore this mechanism should only be used in an environment where all hosts are completely trusted. A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3). When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all. A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user. Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's .rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1). FILES
/etc/hosts.equiv Global trusted host-user pairs list ~/.rhosts Per-user trusted host-user pairs list SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5) HISTORY
The .rhosts file format appeared in 4.2BSD. BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg- ative entries. BSD
November 26, 1997 BSD
Man Page

Featured Tech Videos