BNU files with direct connection in the local system's files

Edit online

These files contain telephone connection entries on the local system zeus.

Systems file: The Systems file on system zeus contains the following entry for the remote system hera:
```
hera Any hera 1200 - "" \r\d\r\d\r in:--in: uzeus word:  thunder
```
This entry specifies that system hera can log in to system zeus at any time, by using a direct connection, which is specified in the Devices files. To find the entry in the Devices files, BNU uses the third and fourth fields of the Systems entry. Thus, BNU looks for an entry in the Devices files with a Type of hera and a Class of 1200. System zeus logs in to system hera as user uzeus with the password thunder.
Devices file: The Devices file on system zeus contains the following entry to connect to the remote system hera:
```
hera    tty5  -  1200  direct
```
This entry specifies that system zeus uses device tty5 at 1200 bps to communicate with system hera. Note that the Dialer in both Dialer-Token Pairs fields is direct. When you connect to system hera, BNU checks the Dialers file for a direct entry.
Dialers file: The Dialers file on system zeus contains the following entry for direct connections:
```
direct
```
This entry specifies that no handshaking is required for direct connection.
Permissions file: The Permissions file on the local system zeus contains the following entry, which specifies the ways in which the remote system hera can conduct uucico and uuxqt transactions with system zeus:
```
LOGNAME=uhera MACHINE=hera VALIDATE=uhera REQUEST=yes \
SENDFILES=yes MACHINE=zeus READ=/ WRITE=/ COMMANDS=ALL
```
This entry specifies that system hera logs in as uhera. Because the VALIDATE=uhera option is included, system hera cannot log in to system zeus with any other login ID, nor can any other remote system use the uhera ID. System hera can read and write to any directory on system zeus, and can send and request files regardless of who initiated the call. System hera can also initiate any commands on system zeus.
Note: Because the permissions that are granted are the same regardless of which system initiated the connection, the LOGNAME and MACHINE entries have been combined. If the permissions are not the same for system hera and system zeus, the LOGNAME and MACHINE entries are as follows:
```
LOGNAME=uhera REQUEST=yes SENDFILES=yes READ=/ WRITE=/
MACHINE=zeus:hera VALIDATE=uhera READ=/ WRITE=/ REQUEST=yes \
COMMANDS=ALL
```
Attention: Providing the permissions in the preceding example is equivalent to giving any user on the remote system a login ID on the local system. Such liberal permissions can jeopardize your security and are given only to well-trusted remote systems at the same site.