iruserok(), iruserok_sa()

Check the identity of a remote host

Synopsis:

#include <unistd.h>

int iruserok( uint32_t raddr, 
              int superuser,
              char * ruser,
              char * luser );

int iruserok_sa( const void * raddr, 
                 int superuser,
                 int rlen,
                 char * ruser,
                 char * luser );

Since:

BlackBerry 10.0.0

Arguments:

raddr
The IP address of the remote host. For iruserok_sa(), this argument is specified as void * to avoid dependencies between <unistd.h> and <sys/socket.h>.
rlen
(iruserok_sa() only) The length of the IP address that raddr points to.
superuser
Nonzero if the local user is the superuser, zero otherwise.
ruser
The name of the remote user.
luser
The name of the local user.

Library:

libsocket

Use the -l socket option to qcc to link against this library.

Description:

The iruserok() routine checks the identity of a remote host. It's used by servers to authenticate clients requesting service with rcmd().

The iruserok() function takes a remote host's IP address, two user names, and a flag indicating whether the local user's name is that of the superuser. Then, if the user isn't the superuser, it checks the file /etc/hosts.equiv (described in the Utilities Reference).

If that lookup isn't done, or is unsuccessful, the .rhosts file in the local user's home directory is checked to see if the request for service is allowed. If this file is owned by anyone other than the user or the superuser, or if it's writable by anyone other than the owner, the check automatically fails.

The iruserok() function can handle only IPv4 addresses; iruserok_sa() and ruserok() can handle other address families as well.

Returns:

0
The machine name is listed in the hosts.equiv file, or the host and remote username were found in the .rhosts file.
-1
An error occurred ( errno is set).

Errors:

The error code EAGAIN is overloaded to mean "All network ports in use."

Classification:

Unix

Safety:  
Cancellation point Yes
Interrupt handler No
Signal handler No
Thread No

Last modified: 2014-06-24



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus