Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ (8) — Plan9 4th Edition

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ftpfs(4)

IPSERV(8)

NAME

telnetd, rlogind, rexexec, ftpd − Internet remote access daemons

SYNOPSIS

­ip/telnetd [-adnptN] [-u user]

­ip/rlogind

­ip/rexexec

­ip/ftpd [-eadp] [-n namepace-file]

DESCRIPTION

These programs support remote access across the Internet.  All expect the network connection to be standard input, output, and error.  They are normally started from scripts in ­/rc/bin/service (see listen(8)).

­Telnetd allows login from a remote client.  There are three types of login:

­normal Normal users log in by encrypting and returning a challenge printed by telnetd. The user can use either the netkey program (see passwd(1)) or a  SecureNet handheld authenticator to encrypt the challenge. ­/lib/namespace defines the namespace. 

­noworld Users in group ­noworld in /adm/users authenticate with a password in the clear.  ­/lib/namespace.noworld defines the namespace. 

­anonymous User ­none requires no authentication.  ­/lib/namespace defines the namespace. 

The options are:

­a allow anonymous login by ­none

­d print debugging to standard error

­p don’t originate any telnet control codes

­n turn on local character echoing and imply the ­p option

­t trusted, that is, don’t authenticate

­u use ­user as the local account name

­N permit connections by ‘noworld’ users only. 

­Rlogind logs in using the BSD remote login protocol.  ­Rlogind execs ­telnetd ­-nu after completing its initial handshake. 

­Rexexec executes a command locally for a remote client.  It uses the standard Plan 9 authentication (see authsrv(6)).

­Ftpd runs the Internet file transfer protocol.  Users may transfer files in either direction between the local and remote machines.  As for telnetd, there are three types of login:

­normal Normal users authenticate via the same challenge/response as for telnetd. /usr/username/lib/namespace.ftp or, if that file does not exist, ­/lib/namespace defines the namespace. 

­noworld Users in group ­noworld in ­/adm/users login using a password in the clear.  ­/lib/namespace.noworld defines the namespace. 

­anonymous Users ­anonymous and ­none require no authentication.  The argument to the ­−n option (default /lib/namespace.ftp) defines the namespace. Anonymous users may only store files in the subtree below /incoming. 

The options are:

­a allow anonymous access

­n the namespace for anonymous users (default /lib/namespace.ftp)

­d write debugging output to standard error

­e treat any user as anonymous

To preserve intended protections in shared file trees, any directory containing a file ­.httplogin is locked by ftpd; see httpd(8).

­Imap4d provides access to a user’s mailboxes via the IMAP4rev1 protocol.  Only files rooted in /mail/box/username/ are accessible.  The list of subscribed mailboxes is contained in /mail/box/username/imap.subscribed, and initially contains only INBOX, IMAP’s name for the user’s mailbox.  A shadow file, mailbox.imp, is created for each mailbox examined. 

The options are:

­a Assume the user is already authenticated.  By default, the user must authenticate using CRAM-MD5 or securenet(8) challenge/response authentication.

­p Allow login authentication.  This option should only be enabled for servers using an encrypted connection, such as SSL, and when enabled, all non-encrypted connections should be disallowed.  ­Imap4d does not enforce this policy. 

­s The server’s name.  If none is provided, ­cs (see ndb(8)) is queried or ­/env/sysname is used. 

­d The local mail domain.  Defaults to the server ­/env/site in the mail server’s domain. 

FILES

­/lib/namepace
/usr/username/lib/namespace.ftp
­/lib/namespace.world
­/lib/namespace.ftp
/mail/box/username/mailbox
/mail/box/username/mailbox.imp
/mail/box/username/imap.subscribed

SOURCE

­/sys/src/cmd/ip/telnetd.c
­/sys/src/cmd/ip/rlogind.c
­/sys/src/cmd/ip/rexexec.c
­/sys/src/cmd/ip/ftpd.c
­/sys/src/cmd/ip/imap4d/

SEE ALSO

ftpfs(4)

Plan 9  —  September 22, 2004

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026