3 .\" Manual for the peer configuration file
5 .\" (c) 2008 Straylight/Edgeware
8 .\"----- Licensing notice ---------------------------------------------------
10 .\" This file is part of Trivial IP Encryption (TrIPE).
12 .\" TrIPE is free software; you can redistribute it and/or modify
13 .\" it under the terms of the GNU General Public License as published by
14 .\" the Free Software Foundation; either version 2 of the License, or
15 .\" (at your option) any later version.
17 .\" TrIPE is distributed in the hope that it will be useful,
18 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
19 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 .\" GNU General Public License for more details.
22 .\" You should have received a copy of the GNU General Public License
23 .\" along with TrIPE; if not, write to the Free Software Foundation,
24 .\" Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
26 .\"--------------------------------------------------------------------------
27 .so ../defs.man.in \"@@@PRE@@@
29 .\"--------------------------------------------------------------------------
30 .TH peers.in 5 "27 March 2008" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
32 .\"--------------------------------------------------------------------------
35 peers.in \- source form for TrIPE peer database
37 .\"--------------------------------------------------------------------------
42 file is a plain text configuration file. It is read by
43 .BR tripe-newpeers (8)
44 in order to produce the
46 database used by services and other tools.
47 .SS "General structure"
48 The configuration file is line-oriented. Blank lines are ignored; lines
53 are ignored. The file is divided into sections by section headers,
54 which are lines of the form
58 Within each section are a number of assignments, of the form
62 or (entirely equivalent)
68 must start in the left hand column. The
70 may span multiple lines if subsequent lines begin with whitespace, in
71 the manner of RFC822 headers.
73 There is a special case to be aware of: if a section doesn't specify a
76 then the section's own name is used as a default.
78 The following substitutions are made in the body of a value.
82 is replaced by the value assigned to the given
87 is replaced by the IP address of the named
95 There is a simple concept of
97 for sections. If a section contains an assignment
99 .BI "@inherits = " parent
101 then any lookups which can't be satisfied in that section will be
102 satisfied instead from the
104 section (and, if necessary, its parent in turn, and so on). Note that
106 substitutions in the resulting value will be satisfied from the original
107 section (though falling back to scanning the parent section). For
108 example, given the sections
112 blurb = expand $(detail)
115 Apart from its effect on lookups, as just described, the
117 key is entirely ignored. In particular, it is never written to the
119 .SS "Standard keys and their meanings"
120 The following keys have meanings to programs in the TrIPE suite. Other
121 keys may be used by separately distributed extensions or for local use.
122 The descriptions given are summaries only; see the references for
126 If true, include the peer in the
129 .BR tripe-newpeers (8);
133 Peer will make active connection as
136 .BR tripe-newpeers (8);
139 This section describes how the textual
141 file is converted into the
145 The handling of each section depends on its name.
147 Sections whose names have the form
149 are ignored (though their contents may be relevant if the section is
150 named in another section's
154 Sections whose names have the form
156 are written to local-type database records with the same name. The keys
157 and values defined in the section (and its parent section, if it
160 key) are stored in the record using
162 as defined in RFC1822, except that the key-value pairs are separated by
165 rather than ampersands
169 key-value pair is not written to the database.
171 Other sections are written to peer-type database records, named
173 in exactly the same way as for local-type records. However, two special
174 actions are also taken.
176 Firstly, if there is a key
178 in the section (or in its parent, etc.), and the value is
186 then the section's name is added in the special
190 Secondly, if there is a key
192 in the section (or in its parent, etc.), then a user record
194 is created whose contents is the section name.
196 .\"--------------------------------------------------------------------------
202 .BR tripe-newpeers (8),
206 .\"--------------------------------------------------------------------------
209 Mark Wooding, <mdw@distorted.org.uk>
211 .\"----- That's all, folks --------------------------------------------------