3 .\" Manual for the peer database file format
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 it under
13 .\" the terms of the GNU General Public License as published by the Free
14 .\" Software Foundation; either version 3 of the License, or (at your
15 .\" option) any later version.
17 .\" TrIPE is distributed in the hope that it will be useful, but WITHOUT
18 .\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
19 .\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
22 .\" You should have received a copy of the GNU General Public License
23 .\" along with TrIPE. If not, see <https://www.gnu.org/licenses/>.
25 .\"--------------------------------------------------------------------------
26 .so ../defs.man.in \"@@@PRE@@@
28 .\"--------------------------------------------------------------------------
29 .TH peers.cdb 5tripe "27 March 2008" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
31 .\"--------------------------------------------------------------------------
34 peers.cdb \- compiled peer database
36 .\"--------------------------------------------------------------------------
43 format database containing information about peers in the TrIPE network,
44 and how to connect to them. It is set up by the
45 .BR tripe-newpeers (8)
46 program based on input in a
49 .SS "Database records"
50 The database contains four kinds of records. The type of record can be
51 inferred from the first character of the record's key.
56 The record consists of a collection of key-value
59 format specified by RFC1866, except that key-value pairs are separated
62 characters. Some of the keys have meaning to various tools and
63 services; others are available for local use.
68 The record consists of a peer name (i.e., a name for which a
70 record exists); all characters are significant. User records are used
73 service to map between user names presented to its
75 command and peer names. No particular relationship between TrIPE user
76 names and system users is necessary.
81 The record consists of key-value pairs in
83 format, just as for peer records. Their meaning is currently not
89 The record format is idiosyncratic. The special records currently
90 defined are described below.
92 The following special records are defined.
95 The record contains a list of a space-separated list of peer names
96 (i.e., names for which a
98 record exists). It is read by the
100 service as a list of peers for which active connections should be made
103 .\"--------------------------------------------------------------------------
109 .BR tripe-newpeers (8),
113 .\"--------------------------------------------------------------------------
116 Mark Wooding, <mdw@distorted.org.uk>
118 .\"----- That's all, folks --------------------------------------------------