To get this branch, use:
bzr branch
http://bzr.recompile.se/loggerhead/mandos/trunk
« back to all changes in this revision
Viewing changes to mandos-clients.conf.xml
- browse files at revision 1132
- compare with another revision
- download diff
- download tarball
- view history from revision 1132
- Committer: Teddy Hogeborn
- Date: 2019-07-30 17:03:57 UTC
- Revision ID: teddy@recompile.se-20190730170357-jte0piul5mq7j5pr
Server: Reap zombies created by multiprocessing.Process()
When creating checkers as multiprocessing.Process() objects, the
multiprocessing module also creates a parent process (for the
call_pipe() function) to call the actual checker process, but this
parent process is not reaped. This is not a huge problem, since the
zombie is always reaped automatically the next time the multiprocess
starts a new process, but the zombies can be up to as many as there
have ever been simultaneous checker processes. To fix this, the
process object must be join():ed when they report completion of the
child checker process.
* mandos (Client): Fix doc string to correctly state that
Client.checker is a multiprocess.Process() and not
a subprocess.Popen() object.
(Client.checker_callback): After the returncode of the checker
process has been read, wait for the
self.checker Process object to finish by
calling join() on it.
Reported-by: Peter Palfrader <weasel@debian.org>
When creating checkers as multiprocessing.Process() objects, the
multiprocessing module also creates a parent process (for the
call_pipe() function) to call the actual checker process, but this
parent process is not reaped. This is not a huge problem, since the
zombie is always reaped automatically the next time the multiprocess
starts a new process, but the zombies can be up to as many as there
have ever been simultaneous checker processes. To fix this, the
process object must be join():ed when they report completion of the
child checker process.
* mandos (Client): Fix doc string to correctly state that
Client.checker is a multiprocess.Process() and not
a subprocess.Popen() object.
(Client.checker_callback): After the returncode of the checker
process has been read, wait for the
self.checker Process object to finish by
calling join() on it.
Reported-by: Peter Palfrader <weasel@debian.org>
- files added:
- .bzr-builddeb
- debian
- debian/po
- debian/source
- debian/tests
- debian/upstream
- dracut-module
- network-hooks.d
- plugin-helpers
- files removed:
- initramfs-tools-hook-conf
- files renamed:
- plugins.d/password-request.c => plugins.d/mandos-client.c
- plugins.d/password-request.xml => plugins.d/mandos-client.xml
- files modified:
- Makefile
added
removed
mandos-clients.conf.xml
1
<?xml version='1.0' encoding='UTF-8'?>
1
<?xml version="1.0" encoding="UTF-8"?>
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
<!ENTITY VERSION "1.0">
5
4
<!ENTITY CONFNAME "mandos-clients.conf">
6
5
<!ENTITY CONFPATH "<filename>/etc/mandos/clients.conf</filename>">
6
<!ENTITY TIMESTAMP "2019-02-10">
7
<!ENTITY % common SYSTEM "common.ent">
8
%common;
7
9
]>
8
10
9
<refentry>
11
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
10
12
<refentryinfo>
11
<title>&CONFNAME;</title>
13
<title>Mandos Manual</title>
12
14
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
13
<productname>&CONFNAME;</productname>
14
<productnumber>&VERSION;</productnumber>
15
<productname>Mandos</productname>
16
<productnumber>&version;</productnumber>
17
<date>&TIMESTAMP;</date>
15
18
<authorgroup>
16
19
<author>
17
20
<firstname>Björn</firstname>
18
21
<surname>Påhlsson</surname>
19
22
<address>
20
<email>belorn@fukt.bsnet.se</email>
23
<email>belorn@recompile.se</email>
21
24
</address>
22
25
</author>
23
26
<author>
24
27
<firstname>Teddy</firstname>
25
28
<surname>Hogeborn</surname>
26
29
<address>
27
<email>teddy@fukt.bsnet.se</email>
30
<email>teddy@recompile.se</email>
28
31
</address>
29
32
</author>
30
33
</authorgroup>
31
34
<copyright>
32
35
<year>2008</year>
36
<year>2009</year>
37
<year>2010</year>
38
<year>2011</year>
39
<year>2012</year>
40
<year>2013</year>
41
<year>2014</year>
42
<year>2015</year>
43
<year>2016</year>
44
<year>2017</year>
45
<year>2018</year>
46
<year>2019</year>
33
47
<holder>Teddy Hogeborn</holder>
34
48
<holder>Björn Påhlsson</holder>
35
49
</copyright>
36
<legalnotice>
37
<para>
38
This manual page is free software: you can redistribute it
39
and/or modify it under the terms of the GNU General Public
40
License as published by the Free Software Foundation,
41
either version 3 of the License, or (at your option) any
42
later version.
43
</para>
44
45
<para>
46
This manual page is distributed in the hope that it will
47
be useful, but WITHOUT ANY WARRANTY; without even the
48
implied warranty of MERCHANTABILITY or FITNESS FOR A
49
PARTICULAR PURPOSE. See the GNU General Public License
50
for more details.
51
</para>
52
53
<para>
54
You should have received a copy of the GNU General Public
55
License along with this program; If not, see
56
<ulink url="http://www.gnu.org/licenses/"/>.
57
</para>
58
</legalnotice>
50
<xi:include href="legalnotice.xml"/>
59
51
</refentryinfo>
60
52
61
53
<refmeta>
62
54
<refentrytitle>&CONFNAME;</refentrytitle>
63
55
<manvolnum>5</manvolnum>
69
61
Configuration file for the Mandos server
70
62
</refpurpose>
71
63
</refnamediv>
72
64
73
65
<refsynopsisdiv>
74
<synopsis>
75
&CONFPATH;
76
</synopsis>
66
<synopsis>&CONFPATH;</synopsis>
77
67
</refsynopsisdiv>
78
68
79
69
<refsect1 id="description">
80
70
<title>DESCRIPTION</title>
81
71
<para>
83
73
><refentrytitle>mandos</refentrytitle>
84
74
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
85
75
The file needs to list all clients that should be able to use
86
the service. All clients listed will be regarded as valid, even
87
if a client was declared invalid in a previous run of the
88
server.
76
the service. The settings in this file can be overridden by
77
runtime changes to the server, which it saves across restarts.
78
(See the section called <quote>PERSISTENT STATE</quote> in
79
<citerefentry><refentrytitle>mandos</refentrytitle><manvolnum
80
>8</manvolnum></citerefentry>.) However, any <emphasis
81
>changes</emphasis> to this file (including adding and removing
82
clients) will, at startup, override changes done during runtime.
89
83
</para>
90
84
<para>
91
85
The format starts with a <literal>[<replaceable>section
115
109
start time expansion, see <xref linkend="expansion"/>.
116
110
</para>
117
111
<para>
118
Uknown options are ignored. The used options are as follows:
112
Unknown options are ignored. The used options are as follows:
119
113
</para>
120
114
121
115
<variablelist>
122
123
<varlistentry>
124
<term><literal><varname>timeout</varname></literal></term>
125
<listitem>
126
<synopsis><literal>timeout = </literal><replaceable
127
>TIME</replaceable>
128
</synopsis>
129
<para>
130
The timeout is how long the server will wait for a
131
successful checker run until a client is considered
132
invalid - that is, ineligible to get the data this server
133
holds. By default Mandos will use 1 hour.
134
</para>
135
<para>
136
The <replaceable>TIME</replaceable> is specified as a
137
space-separated number of values, each of which is a
138
number and a one-character suffix. The suffix must be one
139
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
140
<quote>h</quote>, and <quote>w</quote> for days, seconds,
141
minutes, hours, and weeks, respectively. The values are
142
added together to give the total time value, so all of
143
<quote><literal>330s</literal></quote>,
144
<quote><literal>110s 110s 110s</literal></quote>, and
145
<quote><literal>5m 30s</literal></quote> will give a value
146
of five minutes and thirty seconds.
147
</para>
148
</listitem>
149
</varlistentry>
150
151
<varlistentry>
152
<term><literal><varname>interval</varname></literal></term>
153
<listitem>
154
<synopsis><literal>interval = </literal><replaceable
155
>TIME</replaceable>
156
</synopsis>
157
<para>
158
How often to run the checker to confirm that a client is
159
still up. <emphasis>Note:</emphasis> a new checker will
160
not be started if an old one is still running. The server
161
will wait for a checker to complete until the above
162
<quote><varname>timeout</varname></quote> occurs, at which
163
time the client will be marked invalid, and any running
164
checker killed. The default interval is 5 minutes.
165
</para>
166
<para>
167
The format of <replaceable>TIME</replaceable> is the same
168
as for <varname>timeout</varname> above.
169
</para>
170
</listitem>
171
</varlistentry>
172
173
<varlistentry>
174
<term><literal>checker</literal></term>
175
<listitem>
176
<synopsis><literal>checker = </literal><replaceable
177
>COMMAND</replaceable>
178
</synopsis>
179
<para>
180
This option allows you to override the default shell
181
command that the server will use to check if the client is
182
still up. Any output of the command will be ignored, only
183
the exit code is checked: If the exit code of the command
184
is zero, the client is considered up. The command will be
185
run using <quote><command><filename>/bin/sh</filename>
116
117
<varlistentry>
118
<term><option>approval_delay<literal> = </literal><replaceable
119
>TIME</replaceable></option></term>
120
<listitem>
121
<para>
122
This option is <emphasis>optional</emphasis>.
123
</para>
124
<para>
125
How long to wait for external approval before resorting to
126
use the <option>approved_by_default</option> value. The
127
default is <quote>PT0S</quote>, i.e. not to wait.
128
</para>
129
<para>
130
The format of <replaceable>TIME</replaceable> is the same
131
as for <varname>timeout</varname> below.
132
</para>
133
</listitem>
134
</varlistentry>
135
136
<varlistentry>
137
<term><option>approval_duration<literal> = </literal
138
><replaceable>TIME</replaceable></option></term>
139
<listitem>
140
<para>
141
This option is <emphasis>optional</emphasis>.
142
</para>
143
<para>
144
How long an external approval lasts. The default is 1
145
second.
146
</para>
147
<para>
148
The format of <replaceable>TIME</replaceable> is the same
149
as for <varname>timeout</varname> below.
150
</para>
151
</listitem>
152
</varlistentry>
153
154
<varlistentry>
155
<term><option>approved_by_default<literal> = </literal
156
>{ <literal >1</literal> | <literal>yes</literal> | <literal
157
>true</literal> | <literal>on</literal> | <literal
158
>0</literal> | <literal>no</literal> | <literal
159
>false</literal> | <literal>off</literal> }</option></term>
160
<listitem>
161
<para>
162
Whether to approve a client by default after
163
the <option>approval_delay</option>. The default
164
is <quote>True</quote>.
165
</para>
166
</listitem>
167
</varlistentry>
168
169
<varlistentry>
170
<term><option>checker<literal> = </literal><replaceable
171
>COMMAND</replaceable></option></term>
172
<listitem>
173
<para>
174
This option is <emphasis>optional</emphasis>.
175
</para>
176
<para>
177
This option overrides the default shell command that the
178
server will use to check if the client is still up. Any
179
output of the command will be ignored, only the exit code
180
is checked: If the exit code of the command is zero, the
181
client is considered up. The command will be run using
182
<quote><command><filename>/bin/sh</filename>
186
183
<option>-c</option></command></quote>, so
187
184
<varname>PATH</varname> will be searched. The default
188
185
value for the checker command is <quote><literal
189
186
><command>fping</command> <option>-q</option> <option
190
>--</option> %(host)s</literal></quote>.
187
>--</option> %%(host)s</literal></quote>. Note that
188
<command>mandos-keygen</command>, when generating output
189
to be inserted into this file, normally looks for an SSH
190
server on the Mandos client, and, if it finds one, outputs
191
a <option>checker</option> option to check for the
192
client’s SSH key fingerprint – this is more secure against
193
spoofing.
191
194
</para>
192
195
<para>
193
196
In addition to normal start time expansion, this option
198
201
</varlistentry>
199
202
200
203
<varlistentry>
201
<term><literal>fingerprint</literal></term>
202
<listitem>
203
<synopsis><literal>fingerprint = </literal><replaceable
204
>HEXSTRING</replaceable>
205
</synopsis>
204
<term><option>extended_timeout<literal> = </literal><replaceable
205
>TIME</replaceable></option></term>
206
<listitem>
207
<para>
208
This option is <emphasis>optional</emphasis>.
209
</para>
210
<para>
211
Extended timeout is an added timeout that is given once
212
after a password has been sent successfully to a client.
213
The timeout is by default longer than the normal timeout,
214
and is used for handling the extra long downtime while a
215
machine is booting up. Time to take into consideration
216
when changing this value is file system checks and quota
217
checks. The default value is 15 minutes.
218
</para>
219
<para>
220
The format of <replaceable>TIME</replaceable> is the same
221
as for <varname>timeout</varname> below.
222
</para>
223
</listitem>
224
</varlistentry>
225
226
<varlistentry>
227
<term><option>fingerprint<literal> = </literal
228
><replaceable>HEXSTRING</replaceable></option></term>
229
<listitem>
230
<para>
231
This option is <emphasis>required</emphasis>.
232
</para>
206
233
<para>
207
234
This option sets the OpenPGP fingerprint that identifies
208
235
the public key that clients authenticate themselves with
209
through TLS. The string needs to be in hexidecimal form,
210
but spaces or upper/lower case are not significant.
211
</para>
212
</listitem>
213
</varlistentry>
214
215
<varlistentry>
216
<term><literal>secret</literal></term>
217
<listitem>
218
<synopsis><literal>secret = </literal><replaceable
219
>BASE64_ENCODED_DATA</replaceable>
220
</synopsis>
236
through TLS. The string needs to be in hexadecimal form,
237
but spaces or upper/lower case are not significant.
238
</para>
239
</listitem>
240
</varlistentry>
241
242
<varlistentry>
243
<term><option>key_id<literal> = </literal
244
><replaceable>HEXSTRING</replaceable></option></term>
245
<listitem>
246
<para>
247
This option is <emphasis>optional</emphasis>.
248
</para>
249
<para>
250
This option sets the certificate key ID that identifies
251
the public key that clients authenticate themselves with
252
through TLS. The string needs to be in hexadecimal form,
253
but spaces or upper/lower case are not significant.
254
</para>
255
</listitem>
256
</varlistentry>
257
258
<varlistentry>
259
<term><option><literal>host = </literal><replaceable
260
>STRING</replaceable></option></term>
261
<listitem>
262
<para>
263
This option is <emphasis>optional</emphasis>, but highly
264
<emphasis>recommended</emphasis> unless the
265
<option>checker</option> option is modified to a
266
non-standard value without <quote>%%(host)s</quote> in it.
267
</para>
268
<para>
269
Host name for this client. This is not used by the server
270
directly, but can be, and is by default, used by the
271
checker. See the <option>checker</option> option.
272
</para>
273
</listitem>
274
</varlistentry>
275
276
<varlistentry>
277
<term><option>interval<literal> = </literal><replaceable
278
>TIME</replaceable></option></term>
279
<listitem>
280
<para>
281
This option is <emphasis>optional</emphasis>.
282
</para>
283
<para>
284
How often to run the checker to confirm that a client is
285
still up. <emphasis>Note:</emphasis> a new checker will
286
not be started if an old one is still running. The server
287
will wait for a checker to complete until the below
288
<quote><varname>timeout</varname></quote> occurs, at which
289
time the client will be disabled, and any running checker
290
killed. The default interval is 2 minutes.
291
</para>
292
<para>
293
The format of <replaceable>TIME</replaceable> is the same
294
as for <varname>timeout</varname> below.
295
</para>
296
</listitem>
297
</varlistentry>
298
299
<varlistentry>
300
<term><option>secfile<literal> = </literal><replaceable
301
>FILENAME</replaceable></option></term>
302
<listitem>
303
<para>
304
This option is only used if <option>secret</option> is not
305
specified, in which case this option is
306
<emphasis>required</emphasis>.
307
</para>
308
<para>
309
Similar to the <option>secret</option>, except the secret
310
data is in an external file. The contents of the file
311
should <emphasis>not</emphasis> be base64-encoded, but
312
will be sent to clients verbatim.
313
</para>
314
<para>
315
File names of the form <filename>~user/foo/bar</filename>
316
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
317
are supported.
318
</para>
319
</listitem>
320
</varlistentry>
321
322
<varlistentry>
323
<term><option>secret<literal> = </literal><replaceable
324
>BASE64_ENCODED_DATA</replaceable></option></term>
325
<listitem>
326
<para>
327
If this option is not specified, the <option
328
>secfile</option> option is <emphasis>required</emphasis>
329
to be present.
330
</para>
221
331
<para>
222
332
If present, this option must be set to a string of
223
333
base64-encoded binary data. It will be decoded and sent
224
to the client matching the above
225
<option>fingerprint</option>. This should, of course, be
226
OpenPGP encrypted data, decryptable only by the client.
334
to the client matching the above <option>key_id</option>
335
or <option>fingerprint</option>. This should, of course,
336
be OpenPGP encrypted data, decryptable only by the client.
227
337
The program <citerefentry><refentrytitle><command
228
338
>mandos-keygen</command></refentrytitle><manvolnum
229
339
>8</manvolnum></citerefentry> can, using its
236
346
lines is that a line beginning with white space adds to
237
347
the value of the previous line, RFC 822-style.
238
348
</para>
239
<para>
240
If this option is not specified, the <option
241
>secfile</option> option is used instead, but one of them
242
<emphasis>must</emphasis> be present.
243
</para>
244
</listitem>
245
</varlistentry>
246
247
<varlistentry>
248
<term><literal>secfile</literal></term>
249
<listitem>
250
<synopsis><literal>secfile = </literal><replaceable
251
>FILENAME</replaceable>
252
</synopsis>
253
<para>
254
The same as <option>secret</option>, but the secret data
255
is in an external file. The contents of the file should
256
<emphasis>not</emphasis> be base64-encoded, but will be
257
sent to clients verbatim.
258
</para>
259
<para>
260
This option is only used, and <emphasis>must</emphasis> be
261
present, if <option>secret</option> is not specified.
262
</para>
263
</listitem>
264
</varlistentry>
265
266
<varlistentry>
267
<term><literal>host</literal></term>
268
<listitem>
269
<synopsis><literal>host = </literal><replaceable
270
>STRING</replaceable>
271
</synopsis>
272
<para>
273
Host name for this client. This is not used by the server
274
directly, but can be, and is by default, used by the
275
checker. See the <option>checker</option> option.
349
</listitem>
350
</varlistentry>
351
352
<varlistentry>
353
<term><option>timeout<literal> = </literal><replaceable
354
>TIME</replaceable></option></term>
355
<listitem>
356
<para>
357
This option is <emphasis>optional</emphasis>.
358
</para>
359
<para>
360
The timeout is how long the server will wait, after a
361
successful checker run, until a client is disabled and not
362
allowed to get the data this server holds. By default
363
Mandos will use 5 minutes. See also the
364
<option>extended_timeout</option> option.
365
</para>
366
<para>
367
The <replaceable>TIME</replaceable> is specified as an RFC
368
3339 duration; for example
369
<quote><literal>P1Y2M3DT4H5M6S</literal></quote> meaning
370
one year, two months, three days, four hours, five
371
minutes, and six seconds. Some values can be omitted, see
372
RFC 3339 Appendix A for details.
373
</para>
374
</listitem>
375
</varlistentry>
376
377
<varlistentry>
378
<term><option>enabled<literal> = </literal>{ <literal
379
>1</literal> | <literal>yes</literal> | <literal>true</literal
380
> | <literal >on</literal> | <literal>0</literal> | <literal
381
>no</literal> | <literal>false</literal> | <literal
382
>off</literal> }</option></term>
383
<listitem>
384
<para>
385
Whether this client should be enabled by default. The
386
default is <quote>true</quote>.
276
387
</para>
277
388
</listitem>
278
389
</varlistentry>
279
390
280
391
</variablelist>
281
</refsect1>
392
</refsect1>
282
393
283
394
<refsect1 id="expansion">
284
395
<title>EXPANSION</title>
315
426
<quote><literal>%%(<replaceable>foo</replaceable>)s</literal
316
427
></quote> will be replaced by the value of the attribute
317
428
<varname>foo</varname> of the internal
318
<quote><classname>Client</classname></quote> object. See the
319
source code for details, and let the authors know of any
320
attributes that are useful so they may be preserved to any new
321
versions of this software.
429
<quote><classname>Client</classname></quote> object in the
430
Mandos server. The currently allowed values for
431
<replaceable>foo</replaceable> are:
432
<quote><literal>approval_delay</literal></quote>,
433
<quote><literal>approval_duration</literal></quote>,
434
<quote><literal>created</literal></quote>,
435
<quote><literal>enabled</literal></quote>,
436
<quote><literal>expires</literal></quote>,
437
<quote><literal>key_id</literal></quote>,
438
<quote><literal>fingerprint</literal></quote>,
439
<quote><literal>host</literal></quote>,
440
<quote><literal>interval</literal></quote>,
441
<quote><literal>last_approval_request</literal></quote>,
442
<quote><literal>last_checked_ok</literal></quote>,
443
<quote><literal>last_enabled</literal></quote>,
444
<quote><literal>name</literal></quote>,
445
<quote><literal>timeout</literal></quote>, and, if using
446
D-Bus, <quote><literal>dbus_object_path</literal></quote>.
447
See the source code for details. <emphasis role="strong"
448
>Currently, <emphasis>none</emphasis> of these attributes
449
except <quote><literal>host</literal></quote> are guaranteed
450
to be valid in future versions.</emphasis> Therefore, please
451
let the authors know of any attributes that are useful so they
452
may be preserved to any new versions of this software.
322
453
</para>
323
454
<para>
324
455
Note that this means that, in order to include an actual
327
458
percent characters in a row (<quote>%%%%</quote>) must be
328
459
entered. Also, a bad format here will lead to an immediate
329
460
but <emphasis>silent</emphasis> run-time fatal exit; debug
330
mode is needed to track down an error of this kind.
461
mode is needed to expose an error of this kind.
331
462
</para>
332
463
</refsect2>
333
334
</refsect1>
464
465
</refsect1>
335
466
336
467
<refsect1 id="files">
337
468
<title>FILES</title>
352
483
<literal>%(<replaceable>foo</replaceable>)s</literal> is
353
484
obscure.
354
485
</para>
486
<xi:include href="bugs.xml"/>
355
487
</refsect1>
356
488
357
489
<refsect1 id="example">
359
491
<informalexample>
360
492
<programlisting>
361
493
[DEFAULT]
362
timeout = 1h
363
interval = 5m
364
checker = fping -q -- %(host)s
494
timeout = PT5M
495
interval = PT2M
496
checker = fping -q -- %%(host)s
365
497
366
498
# Client "foo"
367
499
[foo]
500
key_id = 788cd77115cd0bb7b2d5e0ae8496f6b48149d5e712c652076b1fd2d957ef7c1f
368
501
fingerprint = 7788 2722 5BA7 DE53 9C5A 7CFA 59CF F7CD BD9A 5920
369
502
secret =
370
503
hQIOA6QdEjBs2L/HEAf/TCyrDe5Xnm9esa+Pb/vWF9CUqfn4srzVgSu234
383
516
4T2zw4dxS5NswXWU0sVEXxjs6PYxuIiCTL7vdpx8QjBkrPWDrAbcMyBr2O
384
517
QlnHIvPzEArRQLo=
385
518
host = foo.example.org
386
interval = 1m
519
interval = PT1M
387
520
388
521
# Client "bar"
389
522
[bar]
523
key_id = F90C7A81D72D1EA69A51031A91FF8885F36C8B46D155C8C58709A4C99AE9E361
390
524
fingerprint = 3e393aeaefb84c7e89e2f547b3a107558fca3a27
391
525
secfile = /etc/mandos/bar-secret
392
timeout = 15m
393
526
timeout = PT15M
527
approved_by_default = False
528
approval_delay = PT30S
394
529
</programlisting>
395
530
</informalexample>
396
</refsect1>
531
</refsect1>
397
532
398
533
<refsect1 id="see_also">
399
534
<title>SEE ALSO</title>
400
535
<para>
401
<citerefentry>
402
<refentrytitle>mandos</refentrytitle>
403
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
404
<refentrytitle>mandos-keygen</refentrytitle>
405
<manvolnum>8</manvolnum></citerefentry>, <citerefentry>
406
<refentrytitle>mandos.conf</refentrytitle>
407
<manvolnum>5</manvolnum></citerefentry>
536
<citerefentry><refentrytitle>intro</refentrytitle>
537
<manvolnum>8mandos</manvolnum></citerefentry>,
538
<citerefentry><refentrytitle>mandos-keygen</refentrytitle>
539
<manvolnum>8</manvolnum></citerefentry>,
540
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
541
<manvolnum>5</manvolnum></citerefentry>,
542
<citerefentry><refentrytitle>mandos</refentrytitle>
543
<manvolnum>8</manvolnum></citerefentry>,
544
<citerefentry><refentrytitle>fping</refentrytitle>
545
<manvolnum>8</manvolnum></citerefentry>
408
546
</para>
547
<variablelist>
548
<varlistentry>
549
<term>
550
RFC 3339: <citetitle>Date and Time on the Internet:
551
Timestamps</citetitle>
552
</term>
553
<listitem>
554
<para>
555
The time intervals are in the "duration" format, as
556
specified in ABNF in Appendix A of RFC 3339.
557
</para>
558
</listitem>
559
</varlistentry>
560
</variablelist>
409
561
</refsect1>
410
562
</refentry>
563
<!-- Local Variables: -->
564
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
565
<!-- time-stamp-end: "[\"']>" -->
566
<!-- time-stamp-format: "%:y-%02m-%02d" -->
567
<!-- End: -->
Loggerhead is a web-based interface for Breezy
Version: 2.0.2.dev0