Add the DragonFly cvs id and perform general cleanups on cvs/rcs/sccs ids. Most
[dragonfly.git] / contrib / opie / opieinfo.1
CommitLineData
984263bc
MD
1.\" opieinfo.1: Manual page for the opieinfo(1) program.
2.\"
3.\" %%% portions-copyright-cmetz-96
4.\" Portions of this software are Copyright 1996-1999 by Craig Metz, All Rights
5.\" Reserved. The Inner Net License Version 2 applies to these portions of
6.\" the software.
7.\" You should have received a copy of the license with this software. If
8.\" you didn't get a copy, you may request one from <license@inner.net>.
9.\"
10.\" Portions of this software are Copyright 1995 by Randall Atkinson and Dan
11.\" McDonald, All Rights Reserved. All Rights under this copyright are assigned
12.\" to the U.S. Naval Research Laboratory (NRL). The NRL Copyright Notice and
13.\" License Agreement applies to this software.
14.\"
15.\" History:
16.\"
17.\" Modified by cmetz for OPIE 2.2. Removed MJR DES documentation.
18.\" Modified at NRL for OPIE 2.0.
19.\" Written at Bellcore for the S/Key Version 1 software distribution
20.\" (keyinfo.1).
21.\"
22.\" $FreeBSD: src/contrib/opie/opieinfo.1,v 1.3.6.4 2002/07/15 14:48:43 des Exp $
1de703da 23.\" $DragonFly: src/contrib/opie/opieinfo.1,v 1.2 2003/06/17 04:24:05 dillon Exp $
984263bc
MD
24.ll 6i
25.pl 10.5i
26.lt 6.0i
27.TH OPIEINFO 1 "January 10, 1995"
28.AT 3
29.SH NAME
30opieinfo \- Extract sequence number and seed for future OPIE challenges.
31
32.SH SYNOPSIS
33.B opieinfo
34[\-v] [\-h] [
35.I user_name
36]
37
38.SH DESCRIPTION
39.I opieinfo
40takes an optional user name and writes the current sequence number
41and seed found in the OPIE key database for either the current user
42or the user specified. opiekey is compatible with the
43.IR keyinfo (1)
44program
45from Bellcore's S/Key Version 1 except that specification of a remote
46system name is not permitted.
47.sp
48.I opieinfo
49can be used to generate a listing of your future OPIE responses
50if you are going to be without an OPIE calculator and still need to log into
51the system. To do so, you would run something like:
52.sp
53.B opiekey \-n 42 `opieinfo`
54
55.SH OPTIONS
56.TP
57.B \-v
58Display the version number and compile-time options, then exit.
59.TP
60.B \-h
61Display a brief help message and exit.
62.TP
63.B <user_name>
64The name of a user whose key information you wish to display. The default is
65the user running opieinfo.
66
67.SH EXAMPLE
68.sp 0
69wintermute$ opieinfo
70.sp 0
71495 wi01309
72.sp 0
73wintermute$
74.LP
75
76.SH FILES
77.TP
78/etc/opiekeys -- database of key information for the OPIE system.
79
80.SH SEE ALSO
81.BR opie (4),
82.BR opiekey (1),
83.BR opiepasswd (1),
84.BR su (1),
85.BR login (1),
86.BR ftpd (8),
87.BR opiekeys (5)
88.BR opieaccess (5)
89
90.SH AUTHOR
91Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden
92of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan McDonald, and
93Craig Metz.
94
95S/Key is a trademark of Bell Communications Research (Bellcore).
96
97.SH CONTACT
98OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join,
99send an email request to:
100.sp
101skey-users-request@thumper.bellcore.com