68
49
<refname><filename>&CONFNAME;</filename></refname>
70
Configuration file for Mandos clients
51
Configuration file for the Mandos server
56
<synopsis>&CONFPATH;</synopsis>
80
59
<refsect1 id="description">
81
60
<title>DESCRIPTION</title>
83
The file &CONFPATH; is the configuration file for mandos where
84
each client that will be abel to use the service need to be
85
specified. The configuration file is looked on at the startup of
86
the service, so to reenable timedout clients one need to only
87
restart the server. The format starts with a section under []
88
which is eather <literal>[DEFAULT]</literal> or a client
89
name. Values is set through the use of VAR = VALUE pair. Values
62
The file &CONFPATH; is a configuration file for <citerefentry
63
><refentrytitle>mandos</refentrytitle>
64
<manvolnum>8</manvolnum></citerefentry>, read by it at startup.
65
The file needs to list all clients that should be able to use
66
the service. All clients listed will be regarded as valid, even
67
if a client was declared invalid in a previous run of the
71
The format starts with a <literal>[<replaceable>section
72
header</replaceable>]</literal> which is either
73
<literal>[DEFAULT]</literal> or <literal>[<replaceable>client
74
name</replaceable>]</literal>. The <replaceable>client
75
name</replaceable> can be anything, and is not tied to a host
76
name. Following the section header is any number of
77
<quote><varname><replaceable>option</replaceable
78
></varname>=<replaceable>value</replaceable></quote> entries,
79
with continuations in the style of RFC 822. <quote><varname
80
><replaceable>option</replaceable></varname>: <replaceable
81
>value</replaceable></quote> is also accepted. Note that
82
leading whitespace is removed from values. Values can contain
83
format strings which refer to other values in the same section,
84
or values in the <quote>DEFAULT</quote> section (see <xref
85
linkend="expansion"/>). Lines beginning with <quote>#</quote>
86
or <quote>;</quote> are ignored and may be used to provide
94
<refsect1 id="default">
95
<title>DEFAULTS</title>
97
The paramters for <literal>[DEFAULT]</literal> are:
91
<refsect1 id="options">
92
<title>OPTIONS</title>
94
<emphasis>Note:</emphasis> all option values are subject to
95
start time expansion, see <xref linkend="expansion"/>.
98
Unknown options are ignored. The used options are as follows:
103
<term><literal>timeout</literal></term>
106
This option allows you to override the default timeout
107
that clients will get. By default mandos will use 1hr.
113
<term><literal>interval</literal></term>
116
This option allows you to override the default interval
117
used between checkups for disconnected clients. By default
124
<term><literal>checker</literal></term>
104
<term><option>timeout<literal> = </literal><replaceable
105
>TIME</replaceable></option></term>
108
This option is <emphasis>optional</emphasis>.
111
The timeout is how long the server will wait (for either a
112
successful checker run or a client receiving its secret)
113
until a client is considered invalid - that is, ineligible
114
to get the data this server holds. By default Mandos will
118
The <replaceable>TIME</replaceable> is specified as a
119
space-separated number of values, each of which is a
120
number and a one-character suffix. The suffix must be one
121
of <quote>d</quote>, <quote>s</quote>, <quote>m</quote>,
122
<quote>h</quote>, and <quote>w</quote> for days, seconds,
123
minutes, hours, and weeks, respectively. The values are
124
added together to give the total time value, so all of
125
<quote><literal>330s</literal></quote>,
126
<quote><literal>110s 110s 110s</literal></quote>, and
127
<quote><literal>5m 30s</literal></quote> will give a value
128
of five minutes and thirty seconds.
134
<term><option>interval<literal> = </literal><replaceable
135
>TIME</replaceable></option></term>
138
This option is <emphasis>optional</emphasis>.
141
How often to run the checker to confirm that a client is
142
still up. <emphasis>Note:</emphasis> a new checker will
143
not be started if an old one is still running. The server
144
will wait for a checker to complete until the above
145
<quote><varname>timeout</varname></quote> occurs, at which
146
time the client will be marked invalid, and any running
147
checker killed. The default interval is 5 minutes.
150
The format of <replaceable>TIME</replaceable> is the same
151
as for <varname>timeout</varname> above.
157
<term><option>checker<literal> = </literal><replaceable
158
>COMMAND</replaceable></option></term>
161
This option is <emphasis>optional</emphasis>.
127
164
This option allows you to override the default shell
128
command that the server will use to check up if the client
129
is still up. By default mandos will "fping -q -- %%(fqdn)s"
137
<refsect1 id="clients">
138
<title>CLIENTS</title>
140
The paramters for clients are:
146
<term><literal>fingerprint</literal></term>
149
This option sets the openpgp fingerprint that identifies
150
the public certificate that clients authenticates themself
151
through gnutls. The string need to be in hex-decimal form.
157
<term><literal>secret</literal></term>
160
Base 64 encoded OpenPGP encrypted password encrypted by
161
the clients openpgp certificate.
167
<term><literal>secfile</literal></term>
170
Base 64 encoded OpenPGP encrypted password encrypted by
171
the clients openpgp certificate as a binary file.
177
<term><literal>fqdn</literal></term>
180
FQDN, that can be used in for checking that the client is up.
186
<term><literal>checker</literal></term>
189
Shell command that the server will use to check up if a
196
<term><literal>timeout</literal></term>
199
Duration that a client can be down whitout be removed from
208
<refsect1 id="examples">
209
<title>EXAMPLES</title>
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>
170
<option>-c</option></command></quote>, so
171
<varname>PATH</varname> will be searched. The default
172
value for the checker command is <quote><literal
173
><command>fping</command> <option>-q</option> <option
174
>--</option> %%(host)s</literal></quote>.
177
In addition to normal start time expansion, this option
178
will also be subject to runtime expansion; see <xref
179
linkend="expansion"/>.
185
<term><option>fingerprint<literal> = </literal
186
><replaceable>HEXSTRING</replaceable></option></term>
189
This option is <emphasis>required</emphasis>.
192
This option sets the OpenPGP fingerprint that identifies
193
the public key that clients authenticate themselves with
194
through TLS. The string needs to be in hexidecimal form,
195
but spaces or upper/lower case are not significant.
201
<term><option>secret<literal> = </literal><replaceable
202
>BASE64_ENCODED_DATA</replaceable></option></term>
205
If this option is not specified, the <option
206
>secfile</option> option is <emphasis>required</emphasis>
210
If present, this option must be set to a string of
211
base64-encoded binary data. It will be decoded and sent
212
to the client matching the above
213
<option>fingerprint</option>. This should, of course, be
214
OpenPGP encrypted data, decryptable only by the client.
215
The program <citerefentry><refentrytitle><command
216
>mandos-keygen</command></refentrytitle><manvolnum
217
>8</manvolnum></citerefentry> can, using its
218
<option>--password</option> option, be used to generate
222
Note: this value of this option will probably be very
223
long. A useful feature to avoid having unreadably-long
224
lines is that a line beginning with white space adds to
225
the value of the previous line, RFC 822-style.
231
<term><option>secfile<literal> = </literal><replaceable
232
>FILENAME</replaceable></option></term>
235
This option is only used if <option>secret</option> is not
236
specified, in which case this option is
237
<emphasis>required</emphasis>.
240
Similar to the <option>secret</option>, except the secret
241
data is in an external file. The contents of the file
242
should <emphasis>not</emphasis> be base64-encoded, but
243
will be sent to clients verbatim.
246
File names of the form <filename>~user/foo/bar</filename>
247
and <filename>$<envar>ENVVAR</envar>/foo/bar</filename>
254
<term><option><literal>host = </literal><replaceable
255
>STRING</replaceable></option></term>
258
This option is <emphasis>optional</emphasis>, but highly
259
<emphasis>recommended</emphasis> unless the
260
<option>checker</option> option is modified to a
261
non-standard value without <quote>%%(host)s</quote> in it.
264
Host name for this client. This is not used by the server
265
directly, but can be, and is by default, used by the
266
checker. See the <option>checker</option> option.
274
<refsect1 id="expansion">
275
<title>EXPANSION</title>
277
There are two forms of expansion: Start time expansion and
280
<refsect2 id="start_time_expansion">
281
<title>START TIME EXPANSION</title>
283
Any string in an option value of the form
284
<quote><literal>%(<replaceable>foo</replaceable>)s</literal
285
></quote> will be replaced by the value of the option
286
<varname>foo</varname> either in the same section, or, if it
287
does not exist there, the <literal>[DEFAULT]</literal>
288
section. This is done at start time, when the configuration
292
Note that this means that, in order to include an actual
293
percent character (<quote>%</quote>) in an option value, two
294
percent characters in a row (<quote>%%</quote>) must be
298
<refsect2 id="runtime_expansion">
299
<title>RUNTIME EXPANSION</title>
301
This is currently only done for the <varname>checker</varname>
305
Any string in an option value of the form
306
<quote><literal>%%(<replaceable>foo</replaceable>)s</literal
307
></quote> will be replaced by the value of the attribute
308
<varname>foo</varname> of the internal
309
<quote><classname>Client</classname></quote> object. See the
310
source code for details, and let the authors know of any
311
attributes that are useful so they may be preserved to any new
312
versions of this software.
315
Note that this means that, in order to include an actual
316
percent character (<quote>%</quote>) in a
317
<varname>checker</varname> option, <emphasis>four</emphasis>
318
percent characters in a row (<quote>%%%%</quote>) must be
319
entered. Also, a bad format here will lead to an immediate
320
but <emphasis>silent</emphasis> run-time fatal exit; debug
321
mode is needed to expose an error of this kind.
327
<refsect1 id="files">
330
The file described here is &CONFPATH;
337
The format for specifying times for <varname>timeout</varname>
338
and <varname>interval</varname> is not very good.
341
The difference between
342
<literal>%%(<replaceable>foo</replaceable>)s</literal> and
343
<literal>%(<replaceable>foo</replaceable>)s</literal> is
348
<refsect1 id="example">
349
<title>EXAMPLE</title>
210
350
<informalexample>
215
checker = fping -q -- %%(fqdn)s
355
checker = fping -q -- %%(host)s
218
359
fingerprint = 7788 2722 5BA7 DE53 9C5A 7CFA 59CF F7CD BD9A 5920
221
361
hQIOA6QdEjBs2L/HEAf/TCyrDe5Xnm9esa+Pb/vWF9CUqfn4srzVgSu234
222
362
REJMVv7lBSrPE2132Lmd2gqF1HeLKDJRSVxJpt6xoWOChGHg+TMyXDxK+N