NIO CommKit Host Interface Installation and System Administration Manual

3-26

Control Tables (from AT&T 255-110-127)

srvtab

Fixed user ID mapping is also useful for selecting uucp logins based on

originating location. Each of the logins must exist in the /etc/passwd ﬁle and

have /usr/lbin/uucp/uucico as the login shell. This allows you to use the

/etc/uucp ﬁles to restrict resources based on originating area or access point

into the network:

201/colan/host*! uucp /u houucp %s uucico

201/colan/modem*! uucp /u phuucp %s uucico

201/* uucp /u njuucp %s uucico

il/univ/earth uucp /u nnuucp %s uucico

* uucp /u nuucp %s uucico

Restrictive User ID Mapping Ranges

The transparent and translated modes of user ID mapping may be restricted

to a numerical range of user IDs by appending the <uid or >uid sufﬁx to the

user ID mapping ﬁeld speciﬁers. This allows the administrator to restrict

mapping to a range of numerical user IDs on a calling host or host group

basis.

For example, the administrator may block transparent ﬁle transfer access to

a range of administrative logins:

nj/cc/myux*! pupu uR *n>100 /opt/dk/bin/pupu pupu:from:%f

The administrator may have several systems that are commonly adminis-

tered, each with a different user population. In this case, transparent map-

ping could be used for administrative logins and translated mapping for user

logins. If administrative logins are all numerically less than 100, the follow-

ing example shows how three systems (myuxa, myuxb, and myuxc) may

use transparent mapping for user IDs less than 100 and translated mapping

for user IDs greater than 100. No other systems have access to the remote

# transparent administrative mappings

nj/cc/myuxa rl U/vx *n<100 %s -Dsh

nj/cc/myuxb rl U/vx *n<100 %s -Dsh

nj/cc/myuxc rl U/vx *n<100 %s -Dsh

# translated user mappings

nj/cc/myuxa rl U/vx &>100 %s -Dsh

nj/cc/myuxb rl U/vx &>100 %s -Dsh

nj/cc/myuxc rl U/vx &>100 %s -Dsh