69
51
Configuration file for the Mandos server
56
<synopsis>&CONFPATH;</synopsis>
79
59
<refsect1 id="description">
80
60
<title>DESCRIPTION</title>
82
The file &CONFPATH; is the configuration file for <citerefentry
62
The file &CONFPATH; is a configuration file for <citerefentry
83
63
><refentrytitle>mandos</refentrytitle>
84
<manvolnum>8</manvolnum></citerefentry>, read by it at startup,
85
where each client that will be able to use the service needs to
86
be listed. All clients listed will be regarded as valid, even
87
if a client was declared invalid in a previous run of the
64
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
65
The file needs to list all clients that should be able to use
66
the service. All clients listed will be regarded as enabled,
67
even if a client was disabled in a previous run of the server.
91
The format starts with a section under [] which is either
70
The format starts with a <literal>[<replaceable>section
71
header</replaceable>]</literal> which is either
92
72
<literal>[DEFAULT]</literal> or <literal>[<replaceable>client
93
name</replaceable>]</literal>. Following the section is any
94
number of <quote><varname><replaceable>option</replaceable
73
name</replaceable>]</literal>. The <replaceable>client
74
name</replaceable> can be anything, and is not tied to a host
75
name. Following the section header is any number of
76
<quote><varname><replaceable>option</replaceable
95
77
></varname>=<replaceable>value</replaceable></quote> entries,
96
78
with continuations in the style of RFC 822. <quote><varname
97
79
><replaceable>option</replaceable></varname>: <replaceable
98
80
>value</replaceable></quote> is also accepted. Note that
99
81
leading whitespace is removed from values. Values can contain
100
82
format strings which refer to other values in the same section,
101
or values in the <quote>DEFAULT</quote> section. Lines
102
beginning with <quote>#</quote> or <quote>;</quote> are ignored
103
and may be used to provide comments.
83
or values in the <quote>DEFAULT</quote> section (see <xref
84
linkend="expansion"/>). Lines beginning with <quote>#</quote>
85
or <quote>;</quote> are ignored and may be used to provide
107
90
<refsect1 id="options">
108
91
<title>OPTIONS</title>
110
The possible options are:
93
<emphasis>Note:</emphasis> all option values are subject to
94
start time expansion, see <xref linkend="expansion"/>.
97
Unknown options are ignored. The used options are as follows:
116
<term><literal><varname>timeout</varname></literal></term>
103
<term><option>timeout<literal> = </literal><replaceable
104
>TIME</replaceable></option></term>
118
<synopsis><literal>timeout = </literal><replaceable
122
The timeout is how long the server will wait for a
123
successful checker run until a client is considered
124
invalid - that is, ineligible to get the data this server
125
holds. By default Mandos will use 1 hour.
107
This option is <emphasis>optional</emphasis>.
110
The timeout is how long the server will wait (for either a
111
successful checker run or a client receiving its secret)
112
until a client is disabled and not allowed to get the data
113
this server holds. By default Mandos will use 1 hour.
128
116
The <replaceable>TIME</replaceable> is specified as a
144
<term><literal><varname>interval</varname></literal></term>
132
<term><option>interval<literal> = </literal><replaceable
133
>TIME</replaceable></option></term>
146
<synopsis><literal>interval = </literal><replaceable
136
This option is <emphasis>optional</emphasis>.
150
139
How often to run the checker to confirm that a client is
151
140
still up. <emphasis>Note:</emphasis> a new checker will
152
141
not be started if an old one is still running. The server
153
142
will wait for a checker to complete until the above
154
143
<quote><varname>timeout</varname></quote> occurs, at which
155
time the client will be marked invalid, and any running
156
checker killed. The default interval is 5 minutes.
144
time the client will be disabled, and any running checker
145
killed. The default interval is 5 minutes.
159
148
The format of <replaceable>TIME</replaceable> is the same
160
149
as for <varname>timeout</varname> above.
166
<term><literal>checker</literal></term>
155
<term><option>checker<literal> = </literal><replaceable
156
>COMMAND</replaceable></option></term>
159
This option is <emphasis>optional</emphasis>.
169
162
This option allows you to override the default shell
170
command that the server will use to check up if the client
171
is still up. By default mandos will "fping -q -- %%(host)s"
177
<term><literal>fingerprint</literal></term>
180
This option sets the openpgp fingerprint that identifies
181
the public certificate that clients authenticates themself
182
through gnutls. The string need to be in hex-decimal form.
188
<term><literal>secret</literal></term>
191
Base 64 encoded OpenPGP encrypted password encrypted by
192
the clients openpgp certificate.
198
<term><literal>secfile</literal></term>
201
Base 64 encoded OpenPGP encrypted password encrypted by
202
the clients openpgp certificate as a binary file.
208
<term><literal>host</literal></term>
211
Host name that can be used in for checking that the client is up.
217
<term><literal>checker</literal></term>
220
Shell command that the server will use to check up if a
227
<term><literal>timeout</literal></term>
230
Duration that a client can be down whitout be removed from
163
command that the server will use to check if the client is
164
still up. Any output of the command will be ignored, only
165
the exit code is checked: If the exit code of the command
166
is zero, the client is considered up. The command will be
167
run using <quote><command><filename>/bin/sh</filename>
168
<option>-c</option></command></quote>, so
169
<varname>PATH</varname> will be searched. The default
170
value for the checker command is <quote><literal
171
><command>fping</command> <option>-q</option> <option
172
>--</option> %%(host)s</literal></quote>.
175
In addition to normal start time expansion, this option
176
will also be subject to runtime expansion; see <xref
177
linkend="expansion"/>.
183
<term><option>fingerprint<literal> = </literal
184
><replaceable>HEXSTRING</replaceable></option></term>
187
This option is <emphasis>required</emphasis>.
190
This option sets the OpenPGP fingerprint that identifies
191
the public key that clients authenticate themselves with
192
through TLS. The string needs to be in hexidecimal form,
193
but spaces or upper/lower case are not significant.
199
<term><option>secret<literal> = </literal><replaceable
200
>BASE64_ENCODED_DATA</replaceable></option></term>
203
If this option is not specified, the <option
204
>secfile</option> option is <emphasis>required</emphasis>
208
If present, this option must be set to a string of
209
base64-encoded binary data. It will be decoded and sent
210
to the client matching the above
211
<option>fingerprint</option>. This should, of course, be
212
OpenPGP encrypted data, decryptable only by the client.
213
The program <citerefentry><refentrytitle><command
214
>mandos-keygen</command></refentrytitle><manvolnum
215
>8</manvolnum></citerefentry> can, using its
216
<option>--password</option> option, be used to generate
220
Note: this value of this option will probably be very
221
long. A useful feature to avoid having unreadably-long
222
lines is that a line beginning with white space adds to
223
the value of the previous line, RFC 822-style.
229
<term><option>secfile<literal> = </literal><replaceable
230
>FILENAME</replaceable></option></term>
233
This option is only used if <option>secret</option> is not
234
specified, in which case this option is
235
<emphasis>required</emphasis>.
238
Similar to the <option>secret</option>, except the secret
239
data is in an external file. The contents of the file
240
should <emphasis>not</emphasis> be base64-encoded, but
241
will be sent to clients verbatim.
244
File names of the form <filename>~user/foo/bar</filename>
245
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
252
<term><option><literal>host = </literal><replaceable
253
>STRING</replaceable></option></term>
256
This option is <emphasis>optional</emphasis>, but highly
257
<emphasis>recommended</emphasis> unless the
258
<option>checker</option> option is modified to a
259
non-standard value without <quote>%%(host)s</quote> in it.
262
Host name for this client. This is not used by the server
263
directly, but can be, and is by default, used by the
264
checker. See the <option>checker</option> option.
270
<term><option>approved_by_default<literal> = </literal
271
>{ <literal >1</literal> | <literal>yes</literal> | <literal
272
>true</literal> | <literal>on</literal> | <literal
273
>0</literal> | <literal>no</literal> | <literal
274
>false</literal> | <literal>off</literal> }</option></term>
277
Whether to approve a client by default after
278
the <option>approval_delay</option>. The default
279
is <quote>True</quote>.
285
<term><option>approval_delay<literal> = </literal><replaceable
286
>TIME</replaceable></option></term>
289
This option is <emphasis>optional</emphasis>.
292
How long to wait for external approval before resorting to
293
use the <option>approved_by_default</option> value. The
294
default is <quote>0s</quote>, i.e. not to wait.
297
The format of <replaceable>TIME</replaceable> is the same
298
as for <varname>timeout</varname> above.
304
<term><option>approval_duration<literal> = </literal
305
><replaceable>TIME</replaceable></option></term>
308
This option is <emphasis>optional</emphasis>.
311
How long an external approval lasts. The default is 1
315
The format of <replaceable>TIME</replaceable> is the same
316
as for <varname>timeout</varname> above.
239
324
<refsect1 id="expansion">
240
325
<title>EXPANSION</title>