1 .\" opieaccess.5: Manual page describing the /etc/opieaccess file.
3 .\" Portions of this software are Copyright 1995 by Randall Atkinson and Dan
4 .\" McDonald, All Rights Reserved. All Rights under this copyright are assigned
5 .\" to the U.S. Naval Research Laboratory (NRL). The NRL Copyright Notice and
6 .\" License Agreement applies to this software.
10 .\" Written at NRL for OPIE 2.0.
14 .\" @(#)opieaccess.5 2.0 (NRL) 1/10/95
17 .TH OPIEACCESS 5 "January 10, 1995"
20 /etc/opieaccess \- OPIE database of trusted networks
25 file contains a list of networks that are considered trusted by the system as
26 far as security against passive attacks is concerned. Users from networks so
27 trusted will be able to log in using OPIE responses, but not be required to
28 do so, while users from networks that are not trusted will always be required
29 to use OPIE responses (the default behavior). This trust allows a site to
30 have a more gentle migration to OPIE by allowing it to be non-mandatory for
31 "inside" networks while allowing users to choose whether they with to use OPIE
32 to protect their passwords or not.
34 The entire notion of trust implemented in the
36 file is a major security hole because it opens your system back up to the same
37 passive attacks that the OPIE system is designed to protect you against. The
39 support in this version of OPIE exists solely because we believe that it is
40 better to have it so that users who don't want their accounts broken into can
41 use OPIE than to have them prevented from doing so by users who don't want
42 to use OPIE. In any environment, it should be considered a transition tool and
43 not a permanent fixture. When it is not being used as a transition tool, a
44 version of OPIE that has been built without support for the
46 file should be built to prevent the possibility of an attacker using this file
47 as a means to circumvent the OPIE software.
51 file consists of lines containing three fields separated by spaces (tabs are
52 properly interpreted, but spaces should be used instead) as follows:
57 action "permit" or "deny" non-OPIE logins
58 address Address of the network to match
59 mask Mask of the network to match
62 Subnets can be controlled by using the appropriate address and mask. Individual
63 hosts can be controlled by using the appropriate address and a mask of
64 255.255.255.255. If no rules are matched, the default is to deny non-0PIE
77 Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden
78 of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan McDonald, and
81 S/Key is a trademark of Bell Communications Research (Bellcore).
84 OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join,
85 send an email request to:
87 skey-users-request@thumper.bellcore.com