Correct the description of skeyaccess(). It determines whether Unix
passwords are permitted, not whether S/Key passwords are permitted. This manual page could use a good going over.
This commit is contained in:
parent
30b32223e1
commit
757be9d291
@ -22,7 +22,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: skey.3,v 1.6 1997/03/19 01:33:23 bde Exp $
|
||||
.\" $Id: skey.3,v 1.7 1998/03/19 07:34:16 charnier Exp $
|
||||
.\"
|
||||
.Dd December 22, 1996
|
||||
.Dt SKEY 3
|
||||
@ -135,10 +135,12 @@ UNIX password (namely, a string containing ":").
|
||||
.Pp
|
||||
The
|
||||
.Fn skeyaccess
|
||||
function determines whether s/key passwords are permitted for any
|
||||
combination of user name, group member, terminal port, host name or
|
||||
network.
|
||||
See
|
||||
function determines whether traditional UNIX (non-S/Key) passwords
|
||||
are permitted for any combination of user name, group member,
|
||||
terminal port, host name, and network. If UNIX passwords are allowed,
|
||||
.Fn skeyaccess
|
||||
returns a non-zero value. If UNIX passwords are not allowed, it
|
||||
returns 0. See
|
||||
.Xr skey.access 5
|
||||
for more information on the layout and structure of the
|
||||
skey.access configuration file which this function uses.
|
||||
|
Loading…
Reference in New Issue
Block a user