52
69
Configuration file for the Mandos server
57
<synopsis>&CONFPATH;</synopsis>
60
79
<refsect1 id="description">
61
80
<title>DESCRIPTION</title>
63
The file &CONFPATH; is a configuration file for <citerefentry
82
The file &CONFPATH; is the configuration file for <citerefentry
64
83
><refentrytitle>mandos</refentrytitle>
65
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
66
The file needs to list all clients that should be able to use
67
the service. All clients listed will be regarded as enabled,
68
even if a client was disabled in a previous run of the server.
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
71
91
The format starts with a <literal>[<replaceable>section
91
111
<refsect1 id="options">
92
112
<title>OPTIONS</title>
94
<emphasis>Note:</emphasis> all option values are subject to
95
start time expansion, see <xref linkend="expansion"/>.
98
Unknown options are ignored. The used options are as follows:
114
The possible options are:
104
<term><option>approval_delay<literal> = </literal><replaceable
105
>TIME</replaceable></option></term>
108
This option is <emphasis>optional</emphasis>.
111
How long to wait for external approval before resorting to
112
use the <option>approved_by_default</option> value. The
113
default is <quote>0s</quote>, i.e. not to wait.
116
The format of <replaceable>TIME</replaceable> is the same
117
as for <varname>timeout</varname> below.
123
<term><option>approval_duration<literal> = </literal
124
><replaceable>TIME</replaceable></option></term>
127
This option is <emphasis>optional</emphasis>.
130
How long an external approval lasts. The default is 1
134
The format of <replaceable>TIME</replaceable> is the same
135
as for <varname>timeout</varname> below.
141
<term><option>approved_by_default<literal> = </literal
142
>{ <literal >1</literal> | <literal>yes</literal> | <literal
143
>true</literal> | <literal>on</literal> | <literal
144
>0</literal> | <literal>no</literal> | <literal
145
>false</literal> | <literal>off</literal> }</option></term>
148
Whether to approve a client by default after
149
the <option>approval_delay</option>. The default
150
is <quote>True</quote>.
156
<term><option>checker<literal> = </literal><replaceable
157
>COMMAND</replaceable></option></term>
160
This option is <emphasis>optional</emphasis>.
120
<term><literal><varname>timeout</varname></literal></term>
122
<synopsis><literal>timeout = </literal><replaceable
126
The timeout is how long the server will wait for a
127
successful checker run until a client is considered
128
invalid - that is, ineligible to get the data this server
129
holds. By default Mandos will use 1 hour.
132
The <replaceable>TIME</replaceable> is specified as a
133
space-separated number of values, each of which is a
134
number and a one-character suffix. The suffix must be one
135
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
136
<quote>h</quote>, and <quote>w</quote> for days, seconds,
137
minutes, hours, and weeks, respectively. The values are
138
added together to give the total time value, so all of
139
<quote><literal>330s</literal></quote>,
140
<quote><literal>110s 110s 110s</literal></quote>, and
141
<quote><literal>5m 30s</literal></quote> will give a value
142
of five minutes and thirty seconds.
148
<term><literal><varname>interval</varname></literal></term>
150
<synopsis><literal>interval = </literal><replaceable
154
How often to run the checker to confirm that a client is
155
still up. <emphasis>Note:</emphasis> a new checker will
156
not be started if an old one is still running. The server
157
will wait for a checker to complete until the above
158
<quote><varname>timeout</varname></quote> occurs, at which
159
time the client will be marked invalid, and any running
160
checker killed. The default interval is 5 minutes.
163
The format of <replaceable>TIME</replaceable> is the same
164
as for <varname>timeout</varname> above.
170
<term><literal>checker</literal></term>
172
<synopsis><literal>checker = </literal><replaceable
173
>COMMAND</replaceable>
163
176
This option allows you to override the default shell
164
177
command that the server will use to check if the client is
165
still up. Any output of the command will be ignored, only
166
the exit code is checked: If the exit code of the command
167
is zero, the client is considered up. The command will be
168
run using <quote><command><filename>/bin/sh</filename>
169
<option>-c</option></command></quote>, so
170
<varname>PATH</varname> will be searched. The default
171
value for the checker command is <quote><literal
172
><command>fping</command> <option>-q</option> <option
173
>--</option> %%(host)s</literal></quote>.
178
still up. The output of the command will be ignored, only
179
the exit code is checked. The command will be run using
180
<quote><command><filename>/bin/sh</filename>
181
<option>-c</option></command></quote>. The default
182
command is <quote><literal><command>fping</command>
183
<option>-q</option> <option>--</option>
184
%(host)s</literal></quote>.
176
187
In addition to normal start time expansion, this option
200
<term><option><literal>host = </literal><replaceable
201
>STRING</replaceable></option></term>
204
This option is <emphasis>optional</emphasis>, but highly
205
<emphasis>recommended</emphasis> unless the
206
<option>checker</option> option is modified to a
207
non-standard value without <quote>%%(host)s</quote> in it.
210
Host name for this client. This is not used by the server
211
directly, but can be, and is by default, used by the
212
checker. See the <option>checker</option> option.
218
<term><option>interval<literal> = </literal><replaceable
219
>TIME</replaceable></option></term>
222
This option is <emphasis>optional</emphasis>.
225
How often to run the checker to confirm that a client is
226
still up. <emphasis>Note:</emphasis> a new checker will
227
not be started if an old one is still running. The server
228
will wait for a checker to complete until the below
229
<quote><varname>timeout</varname></quote> occurs, at which
230
time the client will be disabled, and any running checker
231
killed. The default interval is 5 minutes.
234
The format of <replaceable>TIME</replaceable> is the same
235
as for <varname>timeout</varname> below.
241
<term><option>secfile<literal> = </literal><replaceable
242
>FILENAME</replaceable></option></term>
245
This option is only used if <option>secret</option> is not
246
specified, in which case this option is
247
<emphasis>required</emphasis>.
250
Similar to the <option>secret</option>, except the secret
251
data is in an external file. The contents of the file
252
should <emphasis>not</emphasis> be base64-encoded, but
253
will be sent to clients verbatim.
256
File names of the form <filename>~user/foo/bar</filename>
257
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
264
<term><option>secret<literal> = </literal><replaceable
265
>BASE64_ENCODED_DATA</replaceable></option></term>
268
If this option is not specified, the <option
269
>secfile</option> option is <emphasis>required</emphasis>
210
<term><literal>secret</literal></term>
212
<synopsis><literal>secret = </literal><replaceable
213
>BASE64_ENCODED_DATA</replaceable>
273
216
If present, this option must be set to a string of
274
217
base64-encoded binary data. It will be decoded and sent
275
218
to the client matching the above
276
219
<option>fingerprint</option>. This should, of course, be
277
220
OpenPGP encrypted data, decryptable only by the client.
278
The program <citerefentry><refentrytitle><command
279
>mandos-keygen</command></refentrytitle><manvolnum
280
>8</manvolnum></citerefentry> can, using its
281
<option>--password</option> option, be used to generate
285
Note: this value of this option will probably be very
286
long. A useful feature to avoid having unreadably-long
287
lines is that a line beginning with white space adds to
288
the value of the previous line, RFC 822-style.
294
<term><option>timeout<literal> = </literal><replaceable
295
>TIME</replaceable></option></term>
298
This option is <emphasis>optional</emphasis>.
301
The timeout is how long the server will wait (for either a
302
successful checker run or a client receiving its secret)
303
until a client is disabled and not allowed to get the data
304
this server holds. By default Mandos will use 1 hour.
307
The <replaceable>TIME</replaceable> is specified as a
308
space-separated number of values, each of which is a
309
number and a one-character suffix. The suffix must be one
310
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
311
<quote>h</quote>, and <quote>w</quote> for days, seconds,
312
minutes, hours, and weeks, respectively. The values are
313
added together to give the total time value, so all of
314
<quote><literal>330s</literal></quote>,
315
<quote><literal>110s 110s 110s</literal></quote>, and
316
<quote><literal>5m 30s</literal></quote> will give a value
317
of five minutes and thirty seconds.
221
<!-- The program <citerefentry><refentrytitle><command -->
222
<!-- >mandos-keygen</command></refentrytitle><manvolnum -->
223
<!-- >8</manvolnum></citerefentry> can be used to generate it, -->
227
Note: this value of this option will probably run over
228
many lines, and will then have to use the fact that a line
229
beginning with white space adds to the value of the
230
previous line, RFC 822-style.
236
<term><literal>secfile</literal></term>
239
Base 64 encoded OpenPGP encrypted password encrypted by
240
the clients openpgp certificate as a binary file.
246
<term><literal>host</literal></term>
249
Host name that can be used in for checking that the client is up.
255
<term><literal>checker</literal></term>
258
Shell command that the server will use to check up if a
265
<term><literal>timeout</literal></term>
268
Duration that a client can be down whitout be removed from
325
277
<refsect1 id="expansion">
326
278
<title>EXPANSION</title>