MFC rev. 1.74: Remove references to S/Key and list OPIE.

This commit is contained in:
yar 2007-05-01 11:46:29 +00:00
parent 8751e4a7b1
commit 676ef2544f

View File

@ -32,7 +32,7 @@
.\" @(#)ftpd.8 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$
.\"
.Dd April 19, 2007
.Dd April 20, 2007
.Dt FTPD 8
.Os
.Sh NAME
@ -355,16 +355,15 @@ The login name must be in the password data base
and not have a null password.
In this case a password must be provided by the client before any
file operations may be performed.
If the user has an S/Key key, the response from a successful USER
command will include an S/Key challenge.
If the user has an OPIE key, the response from a successful USER
command will include an OPIE challenge.
The client may choose to respond with a PASS command giving either
a standard password or an S/Key one-time password.
a standard password or an OPIE one-time password.
The server will automatically determine which type of
password it has been given and attempt to authenticate accordingly.
See
.Xr key 1
for more information on S/Key authentication.
S/Key is a Trademark of Bellcore.
.Xr opie 4
for more information on OPIE authentication.
.It
The login name must not appear in the file
.Pa /etc/ftpusers .
@ -558,9 +557,9 @@ Default place for session logs.
.El
.Sh SEE ALSO
.Xr ftp 1 ,
.Xr key 1 ,
.Xr umask 2 ,
.Xr getusershell 3 ,
.Xr opie 4 ,
.Xr ftpchroot 5 ,
.Xr login.conf 5 ,
.Xr inetd 8 ,