summaryrefslogtreecommitdiff
path: root/usr.bin/skeyinfo/skeyinfo.1
blob: e676caf5610e8fd89ab7d2457a92ef6f5bfb4ae4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
.\" $OpenBSD: skeyinfo.1,v 1.11 2015/02/28 21:51:56 bentley Exp $
.\"
.Dd $Mdocdate: February 28 2015 $
.Dt SKEYINFO 1
.Os
.Sh NAME
.Nm skeyinfo
.Nd obtain the next S/Key challenge for a user
.Sh SYNOPSIS
.Nm skeyinfo
.Op Fl v
.Op Ar user
.Sh DESCRIPTION
.Nm
prints out the next S/Key challenge for the specified user or for the
current user if no user is specified.
.Pp
The options are as follows:
.Bl -tag -width Ds
.It Fl v
Print the hash algorithm as well.
.El
.Sh FILES
.Bl -tag -width /etc/skey
.It Pa /etc/skey
directory containing user entries for S/Key
.El
.Sh EXAMPLES
.Dl $ skey -n <number of passwords to print> `skeyinfo` | lpr
.Pp
This would print out a list of S/Key passwords for use over
an untrusted network (perhaps for use at a conference).
.Sh DIAGNOSTICS
.Bl -tag -width Ds
.It cannot open /etc/skey/user
The user does not have an entry in
.Pa /etc/skey
or access to the S/Key database has been disabled.
The database can be enabled with the
.Xr skeyinit 1
program.
.It user is not listed in /etc/skey
The S/Key database is enabled but the user does not have an entry in it.
The
.Xr skeyinit 1
program can be used to create an entry for the user.
.El
.Sh SEE ALSO
.Xr skey 1 ,
.Xr skeyinit 1