| opieaccess.5 (22348) | opieaccess.5 (22372) |
|---|---|
| 1.\" opieaccess.5: Manual page describing the /etc/opieaccess file. 2.\" 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. 7.\" 8.\" History: 9.\" 10.\" Written at NRL for OPIE 2.0. 11.\" 12.ll 6i 13.pl 10.5i 14.\" @(#)opieaccess.5 2.0 (NRL) 1/10/95 15.\" 16.lt 6.0i 17.TH OPIEACCESS 5 "January 10, 1995" 18.AT 3 19.SH NAME | 1.\" opieaccess.5: Manual page describing the /etc/opieaccess file. 2.\" 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. 7.\" 8.\" History: 9.\" 10.\" Written at NRL for OPIE 2.0. 11.\" 12.ll 6i 13.pl 10.5i 14.\" @(#)opieaccess.5 2.0 (NRL) 1/10/95 15.\" 16.lt 6.0i 17.TH OPIEACCESS 5 "January 10, 1995" 18.AT 3 19.SH NAME |
| 20[/etc/]opieaccess \- OPIE database of trusted networks | 20/etc/opieaccess \- OPIE database of trusted networks |
| 21 22.SH DESCRIPTION 23The 24.I opieaccess 25file contains a list of networks that are considered trusted by the system as 26far as security against passive attacks is concerned. Users from networks so 27trusted will be able to log in using OPIE responses, but not be required to 28do so, while users from networks that are not trusted will always be required --- 31 unchanged lines hidden (view full) --- 60.fi 61 62Subnets can be controlled by using the appropriate address and mask. Individual 63hosts can be controlled by using the appropriate address and a mask of 64255.255.255.255. If no rules are matched, the default is to deny non-0PIE 65logins. 66 67.SH SEE ALSO | 21 22.SH DESCRIPTION 23The 24.I opieaccess 25file contains a list of networks that are considered trusted by the system as 26far as security against passive attacks is concerned. Users from networks so 27trusted will be able to log in using OPIE responses, but not be required to 28do so, while users from networks that are not trusted will always be required --- 31 unchanged lines hidden (view full) --- 60.fi 61 62Subnets can be controlled by using the appropriate address and mask. Individual 63hosts can be controlled by using the appropriate address and a mask of 64255.255.255.255. If no rules are matched, the default is to deny non-0PIE 65logins. 66 67.SH SEE ALSO |
| 68.BR ftpd (8) 69.BR login (1), |
|
| 68.BR opie (4), 69.BR opiekeys (5), 70.BR opiepasswd (1), 71.BR opieinfo (1), | 70.BR opie (4), 71.BR opiekeys (5), 72.BR opiepasswd (1), 73.BR opieinfo (1), |
| 72.BR opiesu (1), 73.BR opielogin (1), 74.BR opieftpd (8) | 74.BR su (1), |
| 75 76.SH AUTHOR 77Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden 78of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan McDonald, and 79Craig Metz. 80 81S/Key is a trademark of Bell Communications Research (Bellcore). 82 83.SH CONTACT 84OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join, 85send an email request to: 86.sp 87skey-users-request@thumper.bellcore.com | 75 76.SH AUTHOR 77Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden 78of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan McDonald, and 79Craig Metz. 80 81S/Key is a trademark of Bell Communications Research (Bellcore). 82 83.SH CONTACT 84OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join, 85send an email request to: 86.sp 87skey-users-request@thumper.bellcore.com |