/mandos/release

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/release

« back to all changes in this revision

Viewing changes to mandos-clients.conf.xml

  • Committer: Teddy Hogeborn
  • Date: 2016-10-05 20:03:48 UTC
  • mfrom: (237.7.425 trunk)
  • Revision ID: teddy@recompile.se-20161005200348-7vio421w006duism
Merge from trunk

Show diffs side-by-side

added added

removed removed

Lines of Context:
3
3
        "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
4
<!ENTITY CONFNAME "mandos-clients.conf">
5
5
<!ENTITY CONFPATH "<filename>/etc/mandos/clients.conf</filename>">
6
 
<!ENTITY TIMESTAMP "2011-10-03">
 
6
<!ENTITY TIMESTAMP "2016-06-23">
7
7
<!ENTITY % common SYSTEM "common.ent">
8
8
%common;
9
9
]>
36
36
      <year>2009</year>
37
37
      <year>2010</year>
38
38
      <year>2011</year>
 
39
      <year>2012</year>
 
40
      <year>2013</year>
 
41
      <year>2014</year>
 
42
      <year>2015</year>
 
43
      <year>2016</year>
39
44
      <holder>Teddy Hogeborn</holder>
40
45
      <holder>Björn Påhlsson</holder>
41
46
    </copyright>
65
70
      ><refentrytitle>mandos</refentrytitle>
66
71
      <manvolnum>8</manvolnum></citerefentry>, read by it at startup.
67
72
      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.
 
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.
70
80
    </para>
71
81
    <para>
72
82
      The format starts with a <literal>[<replaceable>section
111
121
          <para>
112
122
            How long to wait for external approval before resorting to
113
123
            use the <option>approved_by_default</option> value.  The
114
 
            default is <quote>0s</quote>, i.e. not to wait.
 
124
            default is <quote>PT0S</quote>, i.e. not to wait.
115
125
          </para>
116
126
          <para>
117
127
            The format of <replaceable>TIME</replaceable> is the same
161
171
            This option is <emphasis>optional</emphasis>.
162
172
          </para>
163
173
          <para>
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>
 
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>
170
180
            <option>-c</option></command></quote>, so
171
181
            <varname>PATH</varname> will be searched.  The default
172
182
            value for the checker command is <quote><literal
173
183
            ><command>fping</command> <option>-q</option> <option
174
 
            >--</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
 
190
            spoofing.
175
191
          </para>
176
192
          <para>
177
193
            In addition to normal start time expansion, this option
190
206
          </para>
191
207
          <para>
192
208
            Extended timeout is an added timeout that is given once
193
 
            after a password has been sent sucessfully to a client.
 
209
            after a password has been sent successfully to a client.
194
210
            The timeout is by default longer than the normal timeout,
195
211
            and is used for handling the extra long downtime while a
196
212
            machine is booting up.  Time to take into consideration
214
230
          <para>
215
231
            This option sets the OpenPGP fingerprint that identifies
216
232
            the public key that clients authenticate themselves with
217
 
            through TLS.  The string needs to be in hexidecimal form,
 
233
            through TLS.  The string needs to be in hexadecimal form,
218
234
            but spaces or upper/lower case are not significant.
219
235
          </para>
220
236
        </listitem>
329
345
            <option>extended_timeout</option> option.
330
346
          </para>
331
347
          <para>
332
 
            The <replaceable>TIME</replaceable> is specified as a
333
 
            space-separated number of values, each of which is a
334
 
            number and a one-character suffix.  The suffix must be one
335
 
            of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
336
 
            <quote>h</quote>, and <quote>w</quote> for days, seconds,
337
 
            minutes, hours, and weeks, respectively.  The values are
338
 
            added together to give the total time value, so all of
339
 
            <quote><literal>330s</literal></quote>,
340
 
            <quote><literal>110s 110s 110s</literal></quote>, and
341
 
            <quote><literal>5m 30s</literal></quote> will give a value
342
 
            of five minutes and thirty seconds.
 
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.
 
354
          </para>
 
355
        </listitem>
 
356
      </varlistentry>
 
357
      
 
358
      <varlistentry>
 
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>
 
364
        <listitem>
 
365
          <para>
 
366
            Whether this client should be enabled by default.  The
 
367
            default is <quote>true</quote>.
343
368
          </para>
344
369
        </listitem>
345
370
      </varlistentry>
389
414
        <quote><literal>approval_duration</literal></quote>,
390
415
        <quote><literal>created</literal></quote>,
391
416
        <quote><literal>enabled</literal></quote>,
 
417
        <quote><literal>expires</literal></quote>,
392
418
        <quote><literal>fingerprint</literal></quote>,
393
419
        <quote><literal>host</literal></quote>,
394
420
        <quote><literal>interval</literal></quote>,
437
463
      <literal>%(<replaceable>foo</replaceable>)s</literal> is
438
464
      obscure.
439
465
    </para>
 
466
    <xi:include href="bugs.xml"/>
440
467
  </refsect1>
441
468
  
442
469
  <refsect1 id="example">
444
471
    <informalexample>
445
472
      <programlisting>
446
473
[DEFAULT]
447
 
timeout = 5m
448
 
interval = 2m
 
474
timeout = PT5M
 
475
interval = PT2M
449
476
checker = fping -q -- %%(host)s
450
477
 
451
478
# Client "foo"
468
495
        4T2zw4dxS5NswXWU0sVEXxjs6PYxuIiCTL7vdpx8QjBkrPWDrAbcMyBr2O
469
496
        QlnHIvPzEArRQLo=
470
497
host = foo.example.org
471
 
interval = 1m
 
498
interval = PT1M
472
499
 
473
500
# Client "bar"
474
501
[bar]
475
502
fingerprint = 3e393aeaefb84c7e89e2f547b3a107558fca3a27
476
503
secfile = /etc/mandos/bar-secret
477
 
timeout = 15m
 
504
timeout = PT15M
478
505
approved_by_default = False
479
 
approval_delay = 30s
 
506
approval_delay = PT30S
480
507
      </programlisting>
481
508
    </informalexample>
482
509
  </refsect1>
491
518
      <citerefentry><refentrytitle>mandos.conf</refentrytitle>
492
519
      <manvolnum>5</manvolnum></citerefentry>,
493
520
      <citerefentry><refentrytitle>mandos</refentrytitle>
 
521
      <manvolnum>8</manvolnum></citerefentry>,
 
522
      <citerefentry><refentrytitle>fping</refentrytitle>
494
523
      <manvolnum>8</manvolnum></citerefentry>
495
524
    </para>
 
525
    <variablelist>
 
526
      <varlistentry>
 
527
        <term>
 
528
          RFC 3339: <citetitle>Date and Time on the Internet:
 
529
          Timestamps</citetitle>
 
530
        </term>
 
531
      <listitem>
 
532
        <para>
 
533
          The time intervals are in the "duration" format, as
 
534
          specified in ABNF in Appendix A of RFC 3339.
 
535
        </para>
 
536
      </listitem>
 
537
      </varlistentry>
 
538
    </variablelist>
496
539
  </refsect1>
497
540
</refentry>
498
541
<!-- Local Variables: -->