1##################################################
2#
3# $MirSecuCron$
4# $MirOS: src/etc/ppp/ppp.secret.sample,v 1.2 2009/07/18 14:09:12 tg Exp $
5# $OpenBSD: ppp.secret.sample,v 1.4 2002/06/09 06:15:15 todd Exp $
6#
7#          Example of ppp.secret file
8#
9#  This file is used to authenticate incoming connections.
10#  You must ``enable'' either PAP or CHAP in your ppp.conf file.
11#  The peer may then use any of the Authname/Authkey pairs listed.
12#  Additionally, if ``passwdauth'' is enabled and an entry isn't
13#  found in this file, the passwd(5) database is used.
14#
15#  If the password is specified as "*", look it up in passwd(5).
16#  This doesn't work for CHAP connections as ppp must have access
17#  to the unencrypted password for CHAP.
18#
19#  If an IP address or address range is given as the third field, it
20#  will be assigned to the peer.  A ``*'' or an empty field may be
21#  used as a placeholder if you do not wish to override the IP
22#  address, but wish to specify further fields.
23#
24#  If a label is given as the forth field, it is used when reading
25#  the ppp.linkup and ppp.linkdown files.  A ``*'' or an empty field
26#  can be used as a placeholder if you do not wish to override the
27#  label, but wish to specify further fields.
28#
29#  If a phone number or list of phone numbers is given as the fifth
30#  field, these numbers will be used to call back the client if
31#  ``auth'' or ``cbcp'' callback is enabled (see ``set callback'').
32#  A ``*'' specifies that the client must specify the number.
33#
34##################################################
35
36# Authname Authkey      Peer's IP address        Label   Callback
37
38oscar      OurSecretKey 192.2.18.34
39BigBird    X4dWg9327    192.2.18.33/32
40fred       *            *                        fred
41subnet     *            192.2.18.35-192.2.18.70  subnet
42admin      *            *                        *       *
43homeworker *            *                        *       1234567
44