12
13
<title>Mandos Manual</title>
13
14
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
15
<productname>Mandos</productname>
15
<productnumber>&VERSION;</productnumber>
16
<productnumber>&version;</productnumber>
16
17
<date>&TIMESTAMP;</date>
19
20
<firstname>Björn</firstname>
20
21
<surname>Påhlsson</surname>
22
<email>belorn@fukt.bsnet.se</email>
23
<email>belorn@recompile.se</email>
26
27
<firstname>Teddy</firstname>
27
28
<surname>Hogeborn</surname>
29
<email>teddy@fukt.bsnet.se</email>
30
<email>teddy@recompile.se</email>
35
44
<holder>Teddy Hogeborn</holder>
36
45
<holder>Björn Påhlsson</holder>
38
47
<xi:include href="legalnotice.xml"/>
42
51
<refentrytitle>&CONFNAME;</refentrytitle>
43
52
<manvolnum>5</manvolnum>
61
70
><refentrytitle>mandos</refentrytitle>
62
71
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
63
72
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
73
the service. The settings in this file can be overridden by
74
runtime changes to the server, which it saves across restarts.
75
(See the section called <quote>PERSISTENT STATE</quote> in
76
<citerefentry><refentrytitle>mandos</refentrytitle><manvolnum
77
>8</manvolnum></citerefentry>.) However, any <emphasis
78
>changes</emphasis> to this file (including adding and removing
79
clients) will, at startup, override changes done during runtime.
69
82
The format starts with a <literal>[<replaceable>section
93
106
start time expansion, see <xref linkend="expansion"/>.
96
Uknown options are ignored. The used options are as follows:
109
Unknown options are ignored. The used options are as follows:
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.
115
<term><option>approval_delay<literal> = </literal><replaceable
116
>TIME</replaceable></option></term>
119
This option is <emphasis>optional</emphasis>.
122
How long to wait for external approval before resorting to
123
use the <option>approved_by_default</option> value. The
124
default is <quote>PT0S</quote>, i.e. not to wait.
127
The format of <replaceable>TIME</replaceable> is the same
128
as for <varname>timeout</varname> below.
134
<term><option>approval_duration<literal> = </literal
135
><replaceable>TIME</replaceable></option></term>
138
This option is <emphasis>optional</emphasis>.
141
How long an external approval lasts. The default is 1
145
The format of <replaceable>TIME</replaceable> is the same
146
as for <varname>timeout</varname> below.
152
<term><option>approved_by_default<literal> = </literal
153
>{ <literal >1</literal> | <literal>yes</literal> | <literal
154
>true</literal> | <literal>on</literal> | <literal
155
>0</literal> | <literal>no</literal> | <literal
156
>false</literal> | <literal>off</literal> }</option></term>
159
Whether to approve a client by default after
160
the <option>approval_delay</option>. The default
161
is <quote>True</quote>.
148
167
<term><option>checker<literal> = </literal><replaceable
149
168
>COMMAND</replaceable></option></term>
152
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>
171
This option is <emphasis>optional</emphasis>.
174
This option overrides the default shell command that the
175
server will use to check if the client is still up. Any
176
output of the command will be ignored, only the exit code
177
is checked: If the exit code of the command is zero, the
178
client is considered up. The command will be run using
179
<quote><command><filename>/bin/sh</filename>
158
180
<option>-c</option></command></quote>, so
159
181
<varname>PATH</varname> will be searched. The default
160
182
value for the checker command is <quote><literal
161
183
><command>fping</command> <option>-q</option> <option
162
>--</option> %(host)s</literal></quote>.
184
>--</option> %%(host)s</literal></quote>. Note that
185
<command>mandos-keygen</command>, when generating output
186
to be inserted into this file, normally looks for an SSH
187
server on the Mandos client, and, if it find one, outputs
188
a <option>checker</option> option to check for the
189
client’s key fingerprint – this is more secure against
165
193
In addition to normal start time expansion, this option
201
<term><option>extended_timeout<literal> = </literal><replaceable
202
>TIME</replaceable></option></term>
205
This option is <emphasis>optional</emphasis>.
208
Extended timeout is an added timeout that is given once
209
after a password has been sent successfully to a client.
210
The timeout is by default longer than the normal timeout,
211
and is used for handling the extra long downtime while a
212
machine is booting up. Time to take into consideration
213
when changing this value is file system checks and quota
214
checks. The default value is 15 minutes.
217
The format of <replaceable>TIME</replaceable> is the same
218
as for <varname>timeout</varname> below.
173
224
<term><option>fingerprint<literal> = </literal
174
225
><replaceable>HEXSTRING</replaceable></option></term>
228
This option is <emphasis>required</emphasis>.
177
231
This option sets the OpenPGP fingerprint that identifies
178
232
the public key that clients authenticate themselves with
179
233
through TLS. The string needs to be in hexidecimal form,
240
<term><option><literal>host = </literal><replaceable
241
>STRING</replaceable></option></term>
244
This option is <emphasis>optional</emphasis>, but highly
245
<emphasis>recommended</emphasis> unless the
246
<option>checker</option> option is modified to a
247
non-standard value without <quote>%%(host)s</quote> in it.
250
Host name for this client. This is not used by the server
251
directly, but can be, and is by default, used by the
252
checker. See the <option>checker</option> option.
258
<term><option>interval<literal> = </literal><replaceable
259
>TIME</replaceable></option></term>
262
This option is <emphasis>optional</emphasis>.
265
How often to run the checker to confirm that a client is
266
still up. <emphasis>Note:</emphasis> a new checker will
267
not be started if an old one is still running. The server
268
will wait for a checker to complete until the below
269
<quote><varname>timeout</varname></quote> occurs, at which
270
time the client will be disabled, and any running checker
271
killed. The default interval is 2 minutes.
274
The format of <replaceable>TIME</replaceable> is the same
275
as for <varname>timeout</varname> below.
281
<term><option>secfile<literal> = </literal><replaceable
282
>FILENAME</replaceable></option></term>
285
This option is only used if <option>secret</option> is not
286
specified, in which case this option is
287
<emphasis>required</emphasis>.
290
Similar to the <option>secret</option>, except the secret
291
data is in an external file. The contents of the file
292
should <emphasis>not</emphasis> be base64-encoded, but
293
will be sent to clients verbatim.
296
File names of the form <filename>~user/foo/bar</filename>
297
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
186
304
<term><option>secret<literal> = </literal><replaceable
187
305
>BASE64_ENCODED_DATA</replaceable></option></term>
308
If this option is not specified, the <option
309
>secfile</option> option is <emphasis>required</emphasis>
190
313
If present, this option must be set to a string of
191
314
base64-encoded binary data. It will be decoded and sent
192
315
to the client matching the above
204
327
lines is that a line beginning with white space adds to
205
328
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.
334
<term><option>timeout<literal> = </literal><replaceable
335
>TIME</replaceable></option></term>
338
This option is <emphasis>optional</emphasis>.
341
The timeout is how long the server will wait, after a
342
successful checker run, until a client is disabled and not
343
allowed to get the data this server holds. By default
344
Mandos will use 5 minutes. See also the
345
<option>extended_timeout</option> option.
348
The <replaceable>TIME</replaceable> is specified as an RFC
349
3339 duration; for example
350
<quote><literal>P1Y2M3DT4H5M6S</literal></quote> meaning
351
one year, two months, three days, four hours, five
352
minutes, and six seconds. Some values can be omitted, see
353
RFC 3339 Appendix A for details.
359
<term><option>enabled<literal> = </literal>{ <literal
360
>1</literal> | <literal>yes</literal> | <literal>true</literal
361
> | <literal >on</literal> | <literal>0</literal> | <literal
362
>no</literal> | <literal>false</literal> | <literal
363
>off</literal> }</option></term>
366
Whether this client should be enabled by default. The
367
default is <quote>true</quote>.
279
407
<quote><literal>%%(<replaceable>foo</replaceable>)s</literal
280
408
></quote> will be replaced by the value of the attribute
281
409
<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.
410
<quote><classname>Client</classname></quote> object in the
411
Mandos server. The currently allowed values for
412
<replaceable>foo</replaceable> are:
413
<quote><literal>approval_delay</literal></quote>,
414
<quote><literal>approval_duration</literal></quote>,
415
<quote><literal>created</literal></quote>,
416
<quote><literal>enabled</literal></quote>,
417
<quote><literal>expires</literal></quote>,
418
<quote><literal>fingerprint</literal></quote>,
419
<quote><literal>host</literal></quote>,
420
<quote><literal>interval</literal></quote>,
421
<quote><literal>last_approval_request</literal></quote>,
422
<quote><literal>last_checked_ok</literal></quote>,
423
<quote><literal>last_enabled</literal></quote>,
424
<quote><literal>name</literal></quote>,
425
<quote><literal>timeout</literal></quote>, and, if using
426
D-Bus, <quote><literal>dbus_object_path</literal></quote>.
427
See the source code for details. <emphasis role="strong"
428
>Currently, <emphasis>none</emphasis> of these attributes
429
except <quote><literal>host</literal></quote> are guaranteed
430
to be valid in future versions.</emphasis> Therefore, please
431
let the authors know of any attributes that are useful so they
432
may be preserved to any new versions of this software.
288
435
Note that this means that, in order to include an actual
362
510
<refsect1 id="see_also">
363
511
<title>SEE ALSO</title>
513
<citerefentry><refentrytitle>intro</refentrytitle>
514
<manvolnum>8mandos</manvolnum></citerefentry>,
365
515
<citerefentry><refentrytitle>mandos-keygen</refentrytitle>
366
516
<manvolnum>8</manvolnum></citerefentry>,
367
517
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
368
518
<manvolnum>5</manvolnum></citerefentry>,
369
519
<citerefentry><refentrytitle>mandos</refentrytitle>
520
<manvolnum>8</manvolnum></citerefentry>,
521
<citerefentry><refentrytitle>fping</refentrytitle>
370
522
<manvolnum>8</manvolnum></citerefentry>
527
RFC 3339: <citetitle>Date and Time on the Internet:
528
Timestamps</citetitle>
532
The time intervals are in the "duration" format, as
533
specified in ABNF in Appendix A of RFC 3339.
374
540
<!-- Local Variables: -->