47
68
<refname><filename>&CONFNAME;</filename></refname>
49
Configuration file for the Mandos server
70
Configuration file for Mandos clients
54
<synopsis>&CONFPATH;</synopsis>
57
80
<refsect1 id="description">
58
81
<title>DESCRIPTION</title>
60
The file &CONFPATH; is a configuration file for <citerefentry
61
><refentrytitle>mandos</refentrytitle>
62
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
63
The file needs to list all clients that should be able to use
64
the service. All clients listed will be regarded as valid, even
65
if a client was declared invalid in a previous run of the
69
The format starts with a <literal>[<replaceable>section
70
header</replaceable>]</literal> which is either
71
<literal>[DEFAULT]</literal> or <literal>[<replaceable>client
72
name</replaceable>]</literal>. The <replaceable>client
73
name</replaceable> can be anything, and is not tied to a host
74
name. Following the section header is any number of
75
<quote><varname><replaceable>option</replaceable
76
></varname>=<replaceable>value</replaceable></quote> entries,
77
with continuations in the style of RFC 822. <quote><varname
78
><replaceable>option</replaceable></varname>: <replaceable
79
>value</replaceable></quote> is also accepted. Note that
80
leading whitespace is removed from values. Values can contain
81
format strings which refer to other values in the same section,
82
or values in the <quote>DEFAULT</quote> section (see <xref
83
linkend="expansion"/>). Lines beginning with <quote>#</quote>
84
or <quote>;</quote> are ignored and may be used to provide
83
The file &CONFPATH; is the configuration file for mandos where
84
each client that will be abel to use the service need to be
85
specified. The configuration file is looked on at the startup of
86
the service, so to reenable timedout clients one need to only
87
restart the server. The format starts with a section under []
88
which is eather <literal>[DEFAULT]</literal> or a client
89
name. Values is set through the use of VAR = VALUE pair. Values
89
<refsect1 id="options">
90
<title>OPTIONS</title>
92
<emphasis>Note:</emphasis> all option values are subject to
93
start time expansion, see <xref linkend="expansion"/>.
96
Uknown options are ignored. The used options are as follows:
94
<refsect1 id="default">
95
<title>DEFAULTS</title>
97
The paramters for <literal>[DEFAULT]</literal> are:
102
<term><option>timeout<literal> = </literal><replaceable
103
>TIME</replaceable></option></term>
106
The timeout is how long the server will wait for a
107
successful checker run until a client is considered
108
invalid - that is, ineligible to get the data this server
109
holds. By default Mandos will use 1 hour.
112
The <replaceable>TIME</replaceable> is specified as a
113
space-separated number of values, each of which is a
114
number and a one-character suffix. The suffix must be one
115
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
116
<quote>h</quote>, and <quote>w</quote> for days, seconds,
117
minutes, hours, and weeks, respectively. The values are
118
added together to give the total time value, so all of
119
<quote><literal>330s</literal></quote>,
120
<quote><literal>110s 110s 110s</literal></quote>, and
121
<quote><literal>5m 30s</literal></quote> will give a value
122
of five minutes and thirty seconds.
128
<term><option>interval<literal> = </literal><replaceable
129
>TIME</replaceable></option></term>
132
How often to run the checker to confirm that a client is
133
still up. <emphasis>Note:</emphasis> a new checker will
134
not be started if an old one is still running. The server
135
will wait for a checker to complete until the above
136
<quote><varname>timeout</varname></quote> occurs, at which
137
time the client will be marked invalid, and any running
138
checker killed. The default interval is 5 minutes.
141
The format of <replaceable>TIME</replaceable> is the same
142
as for <varname>timeout</varname> above.
148
<term><option>checker<literal> = </literal><replaceable
149
>COMMAND</replaceable></option></term>
103
<term><literal>timeout</literal></term>
106
This option allows you to override the default timeout
107
that clients will get. By default mandos will use 1hr.
113
<term><literal>interval</literal></term>
116
This option allows you to override the default interval
117
used between checkups for disconnected clients. By default
124
<term><literal>checker</literal></term>
152
127
This option allows you to override the default shell
153
command that the server will use to check if the client is
154
still up. Any output of the command will be ignored, only
155
the exit code is checked: If the exit code of the command
156
is zero, the client is considered up. The command will be
157
run using <quote><command><filename>/bin/sh</filename>
158
<option>-c</option></command></quote>, so
159
<varname>PATH</varname> will be searched. The default
160
value for the checker command is <quote><literal
161
><command>fping</command> <option>-q</option> <option
162
>--</option> %(host)s</literal></quote>.
165
In addition to normal start time expansion, this option
166
will also be subject to runtime expansion; see <xref
167
linkend="expansion"/>.
173
<term><option>fingerprint<literal> = </literal
174
><replaceable>HEXSTRING</replaceable></option></term>
177
This option sets the OpenPGP fingerprint that identifies
178
the public key that clients authenticate themselves with
179
through TLS. The string needs to be in hexidecimal form,
180
but spaces or upper/lower case are not significant.
186
<term><option>secret<literal> = </literal><replaceable
187
>BASE64_ENCODED_DATA</replaceable></option></term>
190
If present, this option must be set to a string of
191
base64-encoded binary data. It will be decoded and sent
192
to the client matching the above
193
<option>fingerprint</option>. This should, of course, be
194
OpenPGP encrypted data, decryptable only by the client.
195
The program <citerefentry><refentrytitle><command
196
>mandos-keygen</command></refentrytitle><manvolnum
197
>8</manvolnum></citerefentry> can, using its
198
<option>--password</option> option, be used to generate
202
Note: this value of this option will probably be very
203
long. A useful feature to avoid having unreadably-long
204
lines is that a line beginning with white space adds to
205
the value of the previous line, RFC 822-style.
208
If this option is not specified, the <option
209
>secfile</option> option is used instead, but one of them
210
<emphasis>must</emphasis> be present.
216
<term><option>secfile<literal> = </literal><replaceable
217
>FILENAME</replaceable></option></term>
220
Similar to the <option>secret</option>, except the secret
221
data is in an external file. The contents of the file
222
should <emphasis>not</emphasis> be base64-encoded, but
223
will be sent to clients verbatim.
226
This option is only used, and <emphasis>must</emphasis> be
227
present, if <option>secret</option> is not specified.
233
<term><option><literal>host = </literal><replaceable
234
>STRING</replaceable></option></term>
237
Host name for this client. This is not used by the server
238
directly, but can be, and is by default, used by the
239
checker. See the <option>checker</option> option.
247
<refsect1 id="expansion">
248
<title>EXPANSION</title>
250
There are two forms of expansion: Start time expansion and
253
<refsect2 id="start_time_expansion">
254
<title>START TIME EXPANSION</title>
256
Any string in an option value of the form
257
<quote><literal>%(<replaceable>foo</replaceable>)s</literal
258
></quote> will be replaced by the value of the option
259
<varname>foo</varname> either in the same section, or, if it
260
does not exist there, the <literal>[DEFAULT]</literal>
261
section. This is done at start time, when the configuration
265
Note that this means that, in order to include an actual
266
percent character (<quote>%</quote>) in an option value, two
267
percent characters in a row (<quote>%%</quote>) must be
271
<refsect2 id="runtime_expansion">
272
<title>RUNTIME EXPANSION</title>
274
This is currently only done for the <varname>checker</varname>
278
Any string in an option value of the form
279
<quote><literal>%%(<replaceable>foo</replaceable>)s</literal
280
></quote> will be replaced by the value of the attribute
281
<varname>foo</varname> of the internal
282
<quote><classname>Client</classname></quote> object. See the
283
source code for details, and let the authors know of any
284
attributes that are useful so they may be preserved to any new
285
versions of this software.
288
Note that this means that, in order to include an actual
289
percent character (<quote>%</quote>) in a
290
<varname>checker</varname> option, <emphasis>four</emphasis>
291
percent characters in a row (<quote>%%%%</quote>) must be
292
entered. Also, a bad format here will lead to an immediate
293
but <emphasis>silent</emphasis> run-time fatal exit; debug
294
mode is needed to expose an error of this kind.
300
<refsect1 id="files">
303
The file described here is &CONFPATH;
310
The format for specifying times for <varname>timeout</varname>
311
and <varname>interval</varname> is not very good.
314
The difference between
315
<literal>%%(<replaceable>foo</replaceable>)s</literal> and
316
<literal>%(<replaceable>foo</replaceable>)s</literal> is
321
<refsect1 id="example">
322
<title>EXAMPLE</title>
128
command that the server will use to check up if the client
129
is still up. By default mandos will "fping -q -- %%(host)s"
137
<refsect1 id="clients">
138
<title>CLIENTS</title>
140
The paramters for clients are:
146
<term><literal>fingerprint</literal></term>
149
This option sets the openpgp fingerprint that identifies
150
the public certificate that clients authenticates themself
151
through gnutls. The string need to be in hex-decimal form.
157
<term><literal>secret</literal></term>
160
Base 64 encoded OpenPGP encrypted password encrypted by
161
the clients openpgp certificate.
167
<term><literal>secfile</literal></term>
170
Base 64 encoded OpenPGP encrypted password encrypted by
171
the clients openpgp certificate as a binary file.
177
<term><literal>host</literal></term>
180
Host name that can be used in for checking that the client is up.
186
<term><literal>checker</literal></term>
189
Shell command that the server will use to check up if a
196
<term><literal>timeout</literal></term>
199
Duration that a client can be down whitout be removed from
208
<refsect1 id="examples">
209
<title>EXAMPLES</title>
323
210
<informalexample>
328
checker = fping -q -- %(host)s
215
checker = fping -q -- %%(host)s
332
218
fingerprint = 7788 2722 5BA7 DE53 9C5A 7CFA 59CF F7CD BD9A 5920
334
221
hQIOA6QdEjBs2L/HEAf/TCyrDe5Xnm9esa+Pb/vWF9CUqfn4srzVgSu234
335
222
REJMVv7lBSrPE2132Lmd2gqF1HeLKDJRSVxJpt6xoWOChGHg+TMyXDxK+N