65
72
><refentrytitle>mandos</refentrytitle>
66
73
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
67
74
The file needs to list all clients that should be able to use
68
the service. All clients listed will be regarded as enabled,
69
even if a client was disabled in a previous run of the server.
75
the service. The settings in this file can be overridden by
76
runtime changes to the server, which it saves across restarts.
77
(See the section called <quote>PERSISTENT STATE</quote> in
78
<citerefentry><refentrytitle>mandos</refentrytitle><manvolnum
79
>8</manvolnum></citerefentry>.) However, any <emphasis
80
>changes</emphasis> to this file (including adding and removing
81
clients) will, at startup, override changes done during runtime.
72
84
The format starts with a <literal>[<replaceable>section
161
173
This option is <emphasis>optional</emphasis>.
164
This option allows you to override the default shell
165
command that the server will use to check if the client is
166
still up. Any output of the command will be ignored, only
167
the exit code is checked: If the exit code of the command
168
is zero, the client is considered up. The command will be
169
run using <quote><command><filename>/bin/sh</filename>
176
This option overrides the default shell command that the
177
server will use to check if the client is still up. Any
178
output of the command will be ignored, only the exit code
179
is checked: If the exit code of the command is zero, the
180
client is considered up. The command will be run using
181
<quote><command><filename>/bin/sh</filename>
170
182
<option>-c</option></command></quote>, so
171
183
<varname>PATH</varname> will be searched. The default
172
184
value for the checker command is <quote><literal
173
185
><command>fping</command> <option>-q</option> <option
174
>--</option> %%(host)s</literal></quote>.
186
>--</option> %%(host)s</literal></quote>. Note that
187
<command>mandos-keygen</command>, when generating output
188
to be inserted into this file, normally looks for an SSH
189
server on the Mandos client, and, if it find one, outputs
190
a <option>checker</option> option to check for the
191
client’s key fingerprint – this is more secure against
177
195
In addition to normal start time expansion, this option
203
<term><option>extended_timeout<literal> = </literal><replaceable
204
>TIME</replaceable></option></term>
207
This option is <emphasis>optional</emphasis>.
210
Extended timeout is an added timeout that is given once
211
after a password has been sent successfully to a client.
212
The timeout is by default longer than the normal timeout,
213
and is used for handling the extra long downtime while a
214
machine is booting up. Time to take into consideration
215
when changing this value is file system checks and quota
216
checks. The default value is 15 minutes.
219
The format of <replaceable>TIME</replaceable> is the same
220
as for <varname>timeout</varname> below.
185
226
<term><option>fingerprint<literal> = </literal
186
227
><replaceable>HEXSTRING</replaceable></option></term>
299
340
This option is <emphasis>optional</emphasis>.
302
The timeout is how long the server will wait (for either a
303
successful checker run or a client receiving its secret)
304
until a client is disabled and not allowed to get the data
305
this server holds. By default Mandos will use 5 minutes.
343
The timeout is how long the server will wait, after a
344
successful checker run, until a client is disabled and not
345
allowed to get the data this server holds. By default
346
Mandos will use 5 minutes. See also the
347
<option>extended_timeout</option> option.
308
The <replaceable>TIME</replaceable> is specified as a
309
space-separated number of values, each of which is a
310
number and a one-character suffix. The suffix must be one
311
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
312
<quote>h</quote>, and <quote>w</quote> for days, seconds,
313
minutes, hours, and weeks, respectively. The values are
314
added together to give the total time value, so all of
315
<quote><literal>330s</literal></quote>,
316
<quote><literal>110s 110s 110s</literal></quote>, and
317
<quote><literal>5m 30s</literal></quote> will give a value
318
of five minutes and thirty seconds.
350
The <replaceable>TIME</replaceable> is specified as an RFC
351
3339 duration; for example
352
<quote><literal>P1Y2M3DT4H5M6S</literal></quote> meaning
353
one year, two months, three days, four hours, five
354
minutes, and six seconds. Some values can be omitted, see
355
RFC 3339 Appendix A for details.
324
<term><option>extended_timeout<literal> = </literal><replaceable
325
>TIME</replaceable></option></term>
361
<term><option>enabled<literal> = </literal>{ <literal
362
>1</literal> | <literal>yes</literal> | <literal>true</literal
363
> | <literal >on</literal> | <literal>0</literal> | <literal
364
>no</literal> | <literal>false</literal> | <literal
365
>off</literal> }</option></term>
328
This option is <emphasis>optional</emphasis>.
331
Extended timeout is an added timeout that is given once
332
after a password has been sent sucessfully to a client.
333
The timeout is by default longer than the normal timeout,
334
and is used for handling the extra long downtime while a
335
matchine is booting up. Time to take into consideration
336
when changing this value is system file checks and quota
337
checks. The default value is 15 minutes.
340
The format of <replaceable>TIME</replaceable> is the same
341
as for <varname>timeout</varname> above.
368
Whether this client should be enabled by default. The
369
default is <quote>true</quote>.
388
416
<quote><literal>approval_duration</literal></quote>,
389
417
<quote><literal>created</literal></quote>,
390
418
<quote><literal>enabled</literal></quote>,
419
<quote><literal>expires</literal></quote>,
391
420
<quote><literal>fingerprint</literal></quote>,
392
421
<quote><literal>host</literal></quote>,
393
422
<quote><literal>interval</literal></quote>,
490
520
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
491
521
<manvolnum>5</manvolnum></citerefentry>,
492
522
<citerefentry><refentrytitle>mandos</refentrytitle>
523
<manvolnum>8</manvolnum></citerefentry>,
524
<citerefentry><refentrytitle>fping</refentrytitle>
493
525
<manvolnum>8</manvolnum></citerefentry>
530
RFC 3339: <citetitle>Date and Time on the Internet:
531
Timestamps</citetitle>
535
The time intervals are in the "duration" format, as
536
specified in ABNF in Appendix A of RFC 3339.
497
543
<!-- Local Variables: -->