in.uucpd is invoked by inetd(1M) when a UUCP connection is established, that is, a connection to the port indicated in the "uucp" service specification, and executes the following protocol. See services(4):
If the username is not valid, or is valid but refers to an account that does not have /usr/lib/uucp/uucico as its login shell, or if the password is not the correct password for that account, the connection is dropped. Otherwise, uucico is run, with the user ID, group ID, group set, and home directory for that account, with the environment variables USER and LOGNAME set to the specified username, and with a -u flag specifying the username. Unless the -n flag is specified, entries are made in /var/adm/utmpx and /var/adm/wtmpx for the username. in.uucpd must be invoked by a user with appropriate privilege (usually root) in order to be able to verify that the password is correct.
uucp auth requisite pam_authtok_get.so.1 uucp auth required pam_dhkeys.so.1 uucp auth required pam_unix_auth.so.1 uucp account requisite pam_roles.so.1 uucp account required pam_projects.so.1 uucp account required pam_unix_account.so.1 uucp session required pam_unix_session.so.1
If there are no entries for the uucp service, then the entries for the "other" service will be used. If multiple authentication modules are listed, then the peer may be prompted for multiple passwords.
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibility for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view configuration information for this service. The service's status can be queried using the svcs(1) command.
The pam_unix(5) module is no longer supported. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5).
|November 9, 2015||OmniOS|