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
40
<holder>Teddy Hogeborn</holder>
36
41
<holder>Björn Påhlsson</holder>
38
43
<xi:include href="legalnotice.xml"/>
42
47
<refentrytitle>&CONFNAME;</refentrytitle>
43
48
<manvolnum>5</manvolnum>
61
66
><refentrytitle>mandos</refentrytitle>
62
67
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
63
68
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 service. The settings in this file can be overridden by
70
runtime changes to the server, which it saves across restarts.
71
(See the section called <quote>PERSISTENT STATE</quote> in
72
<citerefentry><refentrytitle>mandos</refentrytitle><manvolnum
73
>8</manvolnum></citerefentry>.) However, any <emphasis
74
>changes</emphasis> to this file (including adding and removing
75
clients) will, at startup, override changes done during runtime.
69
78
The format starts with a <literal>[<replaceable>section
93
102
start time expansion, see <xref linkend="expansion"/>.
96
Uknown options are ignored. The used options are as follows:
105
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.
111
<term><option>approval_delay<literal> = </literal><replaceable
112
>TIME</replaceable></option></term>
115
This option is <emphasis>optional</emphasis>.
118
How long to wait for external approval before resorting to
119
use the <option>approved_by_default</option> value. The
120
default is <quote>PT0S</quote>, i.e. not to wait.
123
The format of <replaceable>TIME</replaceable> is the same
124
as for <varname>timeout</varname> below.
130
<term><option>approval_duration<literal> = </literal
131
><replaceable>TIME</replaceable></option></term>
134
This option is <emphasis>optional</emphasis>.
137
How long an external approval lasts. The default is 1
141
The format of <replaceable>TIME</replaceable> is the same
142
as for <varname>timeout</varname> below.
148
<term><option>approved_by_default<literal> = </literal
149
>{ <literal >1</literal> | <literal>yes</literal> | <literal
150
>true</literal> | <literal>on</literal> | <literal
151
>0</literal> | <literal>no</literal> | <literal
152
>false</literal> | <literal>off</literal> }</option></term>
155
Whether to approve a client by default after
156
the <option>approval_delay</option>. The default
157
is <quote>True</quote>.
148
163
<term><option>checker<literal> = </literal><replaceable
149
164
>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>
167
This option is <emphasis>optional</emphasis>.
170
This option overrides the default shell command that the
171
server will use to check if the client is still up. Any
172
output of the command will be ignored, only the exit code
173
is checked: If the exit code of the command is zero, the
174
client is considered up. The command will be run using
175
<quote><command><filename>/bin/sh</filename>
158
176
<option>-c</option></command></quote>, so
159
177
<varname>PATH</varname> will be searched. The default
160
178
value for the checker command is <quote><literal
161
179
><command>fping</command> <option>-q</option> <option
162
>--</option> %(host)s</literal></quote>.
180
>--</option> %%(host)s</literal></quote>. Note that
181
<command>mandos-keygen</command>, when generating output
182
to be inserted into this file, normally looks for an SSH
183
server on the Mandos client, and, if it find one, outputs
184
a <option>checker</option> option to check for the
185
client’s key fingerprint – this is more secure against
165
189
In addition to normal start time expansion, this option
197
<term><option>extended_timeout<literal> = </literal><replaceable
198
>TIME</replaceable></option></term>
201
This option is <emphasis>optional</emphasis>.
204
Extended timeout is an added timeout that is given once
205
after a password has been sent successfully to a client.
206
The timeout is by default longer than the normal timeout,
207
and is used for handling the extra long downtime while a
208
machine is booting up. Time to take into consideration
209
when changing this value is file system checks and quota
210
checks. The default value is 15 minutes.
213
The format of <replaceable>TIME</replaceable> is the same
214
as for <varname>timeout</varname> below.
173
220
<term><option>fingerprint<literal> = </literal
174
221
><replaceable>HEXSTRING</replaceable></option></term>
224
This option is <emphasis>required</emphasis>.
177
227
This option sets the OpenPGP fingerprint that identifies
178
228
the public key that clients authenticate themselves with
179
229
through TLS. The string needs to be in hexidecimal form,
236
<term><option><literal>host = </literal><replaceable
237
>STRING</replaceable></option></term>
240
This option is <emphasis>optional</emphasis>, but highly
241
<emphasis>recommended</emphasis> unless the
242
<option>checker</option> option is modified to a
243
non-standard value without <quote>%%(host)s</quote> in it.
246
Host name for this client. This is not used by the server
247
directly, but can be, and is by default, used by the
248
checker. See the <option>checker</option> option.
254
<term><option>interval<literal> = </literal><replaceable
255
>TIME</replaceable></option></term>
258
This option is <emphasis>optional</emphasis>.
261
How often to run the checker to confirm that a client is
262
still up. <emphasis>Note:</emphasis> a new checker will
263
not be started if an old one is still running. The server
264
will wait for a checker to complete until the below
265
<quote><varname>timeout</varname></quote> occurs, at which
266
time the client will be disabled, and any running checker
267
killed. The default interval is 2 minutes.
270
The format of <replaceable>TIME</replaceable> is the same
271
as for <varname>timeout</varname> below.
277
<term><option>secfile<literal> = </literal><replaceable
278
>FILENAME</replaceable></option></term>
281
This option is only used if <option>secret</option> is not
282
specified, in which case this option is
283
<emphasis>required</emphasis>.
286
Similar to the <option>secret</option>, except the secret
287
data is in an external file. The contents of the file
288
should <emphasis>not</emphasis> be base64-encoded, but
289
will be sent to clients verbatim.
292
File names of the form <filename>~user/foo/bar</filename>
293
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
186
300
<term><option>secret<literal> = </literal><replaceable
187
301
>BASE64_ENCODED_DATA</replaceable></option></term>
304
If this option is not specified, the <option
305
>secfile</option> option is <emphasis>required</emphasis>
190
309
If present, this option must be set to a string of
191
310
base64-encoded binary data. It will be decoded and sent
192
311
to the client matching the above
204
323
lines is that a line beginning with white space adds to
205
324
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.
330
<term><option>timeout<literal> = </literal><replaceable
331
>TIME</replaceable></option></term>
334
This option is <emphasis>optional</emphasis>.
337
The timeout is how long the server will wait, after a
338
successful checker run, until a client is disabled and not
339
allowed to get the data this server holds. By default
340
Mandos will use 5 minutes. See also the
341
<option>extended_timeout</option> option.
344
The <replaceable>TIME</replaceable> is specified as an RFC
345
3339 duration; for example
346
<quote><literal>P1Y2M3DT4H5M6S</literal></quote> meaning
347
one year, two months, three days, four hours, five
348
minutes, and six seconds. Some values can be omitted, see
349
RFC 3339 Appendix A for details.
355
<term><option>enabled<literal> = </literal>{ <literal
356
>1</literal> | <literal>yes</literal> | <literal>true</literal
357
> | <literal >on</literal> | <literal>0</literal> | <literal
358
>no</literal> | <literal>false</literal> | <literal
359
>off</literal> }</option></term>
362
Whether this client should be enabled by default. The
363
default is <quote>true</quote>.
279
403
<quote><literal>%%(<replaceable>foo</replaceable>)s</literal
280
404
></quote> will be replaced by the value of the attribute
281
405
<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.
406
<quote><classname>Client</classname></quote> object in the
407
Mandos server. The currently allowed values for
408
<replaceable>foo</replaceable> are:
409
<quote><literal>approval_delay</literal></quote>,
410
<quote><literal>approval_duration</literal></quote>,
411
<quote><literal>created</literal></quote>,
412
<quote><literal>enabled</literal></quote>,
413
<quote><literal>expires</literal></quote>,
414
<quote><literal>fingerprint</literal></quote>,
415
<quote><literal>host</literal></quote>,
416
<quote><literal>interval</literal></quote>,
417
<quote><literal>last_approval_request</literal></quote>,
418
<quote><literal>last_checked_ok</literal></quote>,
419
<quote><literal>last_enabled</literal></quote>,
420
<quote><literal>name</literal></quote>,
421
<quote><literal>timeout</literal></quote>, and, if using
422
D-Bus, <quote><literal>dbus_object_path</literal></quote>.
423
See the source code for details. <emphasis role="strong"
424
>Currently, <emphasis>none</emphasis> of these attributes
425
except <quote><literal>host</literal></quote> are guaranteed
426
to be valid in future versions.</emphasis> Therefore, please
427
let the authors know of any attributes that are useful so they
428
may be preserved to any new versions of this software.
288
431
Note that this means that, in order to include an actual
362
506
<refsect1 id="see_also">
363
507
<title>SEE ALSO</title>
509
<citerefentry><refentrytitle>intro</refentrytitle>
510
<manvolnum>8mandos</manvolnum></citerefentry>,
365
511
<citerefentry><refentrytitle>mandos-keygen</refentrytitle>
366
512
<manvolnum>8</manvolnum></citerefentry>,
367
513
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
368
514
<manvolnum>5</manvolnum></citerefentry>,
369
515
<citerefentry><refentrytitle>mandos</refentrytitle>
516
<manvolnum>8</manvolnum></citerefentry>,
517
<citerefentry><refentrytitle>fping</refentrytitle>
370
518
<manvolnum>8</manvolnum></citerefentry>
523
RFC 3339: <citetitle>Date and Time on the Internet:
524
Timestamps</citetitle>
528
The time intervals are in the "duration" format, as
529
specified in ABNF in Appendix A of RFC 3339.
374
536
<!-- Local Variables: -->