68
46
<refname><command>&COMMANDNAME;</command></refname>
70
Sends encrypted passwords to authenticated Mandos clients
48
Gives encrypted passwords to authenticated Mandos clients
76
54
<command>&COMMANDNAME;</command>
77
<arg choice='opt'>--interface<arg choice='plain'>IF</arg></arg>
78
<arg choice='opt'>--address<arg choice='plain'>ADDRESS</arg></arg>
79
<arg choice='opt'>--port<arg choice='plain'>PORT</arg></arg>
80
<arg choice='opt'>--priority<arg choice='plain'>PRIORITY</arg></arg>
81
<arg choice='opt'>--servicename<arg choice='plain'>NAME</arg></arg>
82
<arg choice='opt'>--configdir<arg choice='plain'>DIRECTORY</arg></arg>
83
<arg choice='opt'>--debug</arg>
86
<command>&COMMANDNAME;</command>
87
<arg choice='opt'>-i<arg choice='plain'>IF</arg></arg>
88
<arg choice='opt'>-a<arg choice='plain'>ADDRESS</arg></arg>
89
<arg choice='opt'>-p<arg choice='plain'>PORT</arg></arg>
90
<arg choice='opt'>--priority<arg choice='plain'>PRIORITY</arg></arg>
91
<arg choice='opt'>--servicename<arg choice='plain'>NAME</arg></arg>
92
<arg choice='opt'>--configdir<arg choice='plain'>DIRECTORY</arg></arg>
93
<arg choice='opt'>--debug</arg>
96
<command>&COMMANDNAME;</command>
97
<arg choice='plain'>--help</arg>
100
<command>&COMMANDNAME;</command>
101
<arg choice='plain'>--version</arg>
104
<command>&COMMANDNAME;</command>
105
<arg choice='plain'>--check</arg>
56
<arg choice="plain"><option>--interface
57
<replaceable>NAME</replaceable></option></arg>
58
<arg choice="plain"><option>-i
59
<replaceable>NAME</replaceable></option></arg>
63
<arg choice="plain"><option>--address
64
<replaceable>ADDRESS</replaceable></option></arg>
65
<arg choice="plain"><option>-a
66
<replaceable>ADDRESS</replaceable></option></arg>
70
<arg choice="plain"><option>--port
71
<replaceable>PORT</replaceable></option></arg>
72
<arg choice="plain"><option>-p
73
<replaceable>PORT</replaceable></option></arg>
76
<arg><option>--priority
77
<replaceable>PRIORITY</replaceable></option></arg>
79
<arg><option>--servicename
80
<replaceable>NAME</replaceable></option></arg>
82
<arg><option>--configdir
83
<replaceable>DIRECTORY</replaceable></option></arg>
85
<arg><option>--debug</option></arg>
88
<command>&COMMANDNAME;</command>
90
<arg choice="plain"><option>--help</option></arg>
91
<arg choice="plain"><option>-h</option></arg>
95
<command>&COMMANDNAME;</command>
96
<arg choice="plain"><option>--version</option></arg>
99
<command>&COMMANDNAME;</command>
100
<arg choice="plain"><option>--check</option></arg>
107
102
</refsynopsisdiv>
109
104
<refsect1 id="description">
112
107
<command>&COMMANDNAME;</command> is a server daemon which
113
108
handles incoming request for passwords for a pre-defined list of
114
109
client host computers. The Mandos server uses Zeroconf to
115
announce itself on the local network, and uses GnuTLS to
116
communicate securely with and to authenticate the clients.
117
Mandos uses IPv6 link-local addresses, since the clients are
118
assumed to not have any other addresses configured yet. Any
119
authenticated client is then given the pre-encrypted password
120
for that specific client.
110
announce itself on the local network, and uses TLS to
111
communicate securely with and to authenticate the clients. The
112
Mandos server uses IPv6 to allow Mandos clients to use IPv6
113
link-local addresses, since the clients will probably not have
114
any other addresses configured (see <xref linkend="overview"/>).
115
Any authenticated client is then given the stored pre-encrypted
116
password for that specific client.
125
120
<refsect1 id="purpose">
126
121
<title>PURPOSE</title>
129
123
The purpose of this is to enable <emphasis>remote and unattended
130
rebooting</emphasis> of any client host computer with an
131
<emphasis>encrypted root file system</emphasis>. The client
132
host computer should start a Mandos client in the initial RAM
133
disk environment, the Mandos client program communicates with
134
this server program to get an encrypted password, which is then
135
decrypted and used to unlock the encrypted root file system.
136
The client host computer can then continue its boot sequence
124
rebooting</emphasis> of client host computer with an
125
<emphasis>encrypted root file system</emphasis>. See <xref
126
linkend="overview"/> for details.
142
130
<refsect1 id="options">
143
131
<title>OPTIONS</title>
147
<term><literal>-h</literal>, <literal>--help</literal></term>
134
<term><option>--help</option></term>
135
<term><option>-h</option></term>
150
138
Show a help message and exit
156
<term><literal>-i</literal>, <literal>--interface <replaceable>
157
IF</replaceable></literal></term>
160
Only announce the server and listen to requests on network
161
interface <replaceable>IF</replaceable>. Default is to
162
use all available interfaces.
168
<term><literal>-a</literal>, <literal>--address <replaceable>
169
ADDRESS</replaceable></literal></term>
172
If this option is used, the server will only listen to a
173
specific address. This must currently be an IPv6 address;
174
an IPv4 address can be specified using the
175
"<literal>::FFFF:192.0.2.3</literal>" syntax. Also, if a
176
link-local address is specified, an interface should be
177
set, since a link-local address is only valid on a single
178
interface. By default, the server will listen to all
185
<term><literal>-p</literal>, <literal>--port <replaceable>
186
PORT</replaceable></literal></term>
189
If this option is used, the server to bind to that
190
port. By default, the server will listen to an arbitrary
191
port given by the operating system.
197
<term><literal>--check</literal></term>
200
Run the server's self-tests. This includes any unit
144
<term><option>--interface</option>
145
<replaceable>NAME</replaceable></term>
146
<term><option>-i</option>
147
<replaceable>NAME</replaceable></term>
149
<xi:include href="mandos-options.xml" xpointer="interface"/>
154
<term><option>--address
155
<replaceable>ADDRESS</replaceable></option></term>
157
<replaceable>ADDRESS</replaceable></option></term>
159
<xi:include href="mandos-options.xml" xpointer="address"/>
165
<replaceable>PORT</replaceable></option></term>
167
<replaceable>PORT</replaceable></option></term>
169
<xi:include href="mandos-options.xml" xpointer="port"/>
174
<term><option>--check</option></term>
177
Run the server’s self-tests. This includes any unit
207
<term><literal>--debug</literal></term>
210
If the server is run in debug mode, it will run in the
211
foreground and print a lot of debugging information. The
212
default is <emphasis>not</emphasis> to run in debug mode.
218
<term><literal>--priority <replaceable>
219
PRIORITY</replaceable></literal></term>
222
GnuTLS priority string for the TLS handshake with the
224
<citerefentry><refentrytitle>gnutls_priority_init
225
</refentrytitle><manvolnum>3</manvolnum></citerefentry>
226
for the syntax. The default is
227
"<literal>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal>".
228
<emphasis>Warning</emphasis>: changing this may make the
229
TLS handshake fail, making communication with clients
236
<term><literal>--servicename <replaceable>NAME</replaceable>
240
Zeroconf service name. The default is
241
"<literal>Mandos</literal>". You only need to change this
242
if you for some reason want to run more than one server on
243
the same <emphasis>host</emphasis>. If there are name
244
collisions on the same <emphasis>network</emphasis>, the
245
new server will automatically rename itself to "Mandos
252
<term><literal>--configdir <replaceable>DIR</replaceable>
184
<term><option>--debug</option></term>
186
<xi:include href="mandos-options.xml" xpointer="debug"/>
191
<term><option>--priority <replaceable>
192
PRIORITY</replaceable></option></term>
194
<xi:include href="mandos-options.xml" xpointer="priority"/>
199
<term><option>--servicename
200
<replaceable>NAME</replaceable></option></term>
202
<xi:include href="mandos-options.xml"
203
xpointer="servicename"/>
208
<term><option>--configdir
209
<replaceable>DIRECTORY</replaceable></option></term>
256
212
Directory to search for configuration files. Default is
257
"<literal>/etc/mandos</literal>". See <citerefentry>
258
<refentrytitle>mandos.conf</refentrytitle>
213
<quote><literal>/etc/mandos</literal></quote>. See
214
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
259
215
<manvolnum>5</manvolnum></citerefentry> and <citerefentry>
260
216
<refentrytitle>mandos-clients.conf</refentrytitle>
261
217
<manvolnum>5</manvolnum></citerefentry>.
267
<term><literal>--version</literal></term>
223
<term><option>--version</option></term>
270
226
Prints the program version and exit.
233
<refsect1 id="overview">
234
<title>OVERVIEW</title>
235
<xi:include href="overview.xml"/>
237
This program is the server part. It is a normal server program
238
and will run in a normal system environment, not in an initial
239
<acronym>RAM</acronym> disk environment.
277
243
<refsect1 id="protocol">
278
244
<title>NETWORK PROTOCOL</title>
280
246
The Mandos server announces itself as a Zeroconf service of type
281
"<literal>_mandos._tcp</literal>". The Mandos client connects
282
to the announced address and port, and sends a line of text
283
where the first whitespace-separated field is the protocol
284
version, which currently is "<literal>1</literal>". The client
285
and server then start a TLS protocol handshake with a slight
286
quirk: the Mandos server program acts as a TLS "client" while
287
the connecting Mandos client acts as a TLS "server". The Mandos
288
client must supply an OpenPGP certificate, and the fingerprint
289
of this certificate is used by the Mandos server to look up (in
290
a list read from a file at start time) which binary blob to give
291
the client. No other authentication or authorization is done by
247
<quote><literal>_mandos._tcp</literal></quote>. The Mandos
248
client connects to the announced address and port, and sends a
249
line of text where the first whitespace-separated field is the
250
protocol version, which currently is
251
<quote><literal>1</literal></quote>. The client and server then
252
start a TLS protocol handshake with a slight quirk: the Mandos
253
server program acts as a TLS <quote>client</quote> while the
254
connecting Mandos client acts as a TLS <quote>server</quote>.
255
The Mandos client must supply an OpenPGP certificate, and the
256
fingerprint of this certificate is used by the Mandos server to
257
look up (in a list read from <filename>clients.conf</filename>
258
at start time) which binary blob to give the client. No other
259
authentication or authorization is done by the server.
294
<informaltable><tgroup cols="3"><thead>
262
<title>Mandos Protocol (Version 1)</title><tgroup cols="3"><thead>
296
264
<entry>Mandos Client</entry>
297
265
<entry>Direction</entry>
333
<refsect1 id="environment">
334
<title>ENVIRONMENT</title>
337
<term><envar>PATH</envar></term>
340
To start the configured checker (see <xref
341
linkend="checking"/>), the server uses
342
<filename>/bin/sh</filename>, which in turn uses
343
<varname>PATH</varname> to search for matching commands if
344
an absolute path is not given. See <citerefentry>
345
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
351
353
<refsect1 id="file">
352
354
<title>FILES</title>
356
<filename>/etc/mandos/mandos.conf</filename> See <citerefentry>
357
<refentrytitle>mandos.conf</refentrytitle>
358
<manvolnum>5</manvolnum></citerefentry>.
361
<filename>/etc/mandos/clients.conf</filename> See <citerefentry>
356
Use the <option>--configdir</option> option to change where
357
<command>&COMMANDNAME;</command> looks for its configurations
358
files. The default file names are listed here.
362
<term><filename>/etc/mandos/mandos.conf</filename></term>
365
Server-global settings. See
366
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
367
<manvolnum>5</manvolnum></citerefentry> for details.
372
<term><filename>/etc/mandos/clients.conf</filename></term>
375
List of clients and client-specific settings. See
376
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
377
<manvolnum>5</manvolnum></citerefentry> for details.
382
<term><filename>/var/run/mandos/mandos.pid</filename></term>
385
The file containing the process id of
386
<command>&COMMANDNAME;</command>.
391
<term><filename>/dev/log</filename></term>
394
The Unix domain socket to where local syslog messages are
400
<term><filename>/bin/sh</filename></term>
403
This is used to start the configured checker command for
404
each client. See <citerefentry>
362
405
<refentrytitle>mandos-clients.conf</refentrytitle>
363
<manvolnum>5</manvolnum></citerefentry>.
366
<filename>/var/run/mandos/mandos.pid</filename>
406
<manvolnum>5</manvolnum></citerefentry> for details.
372
413
<refsect1 id="bugs">
373
414
<title>BUGS</title>
378
<refsect1 id="examples">
379
<title>EXAMPLES</title>
416
This server might, on especially fatal errors, emit a Python
417
backtrace. This could be considered a feature.
420
Currently, if a client is declared <quote>invalid</quote> due to
421
having timed out, the server does not record this fact onto
422
permanent storage. This has some security implications, see
423
<xref linkend="CLIENTS"/>.
426
There is currently no way of querying the server of the current
427
status of clients, other than analyzing its <systemitem
428
class="service">syslog</systemitem> output.
431
There is no fine-grained control over logging and debug output.
434
Debug mode is conflated with running in the foreground.
437
The console log messages does not show a timestamp.
441
<refsect1 id="example">
442
<title>EXAMPLE</title>
445
Normal invocation needs no options:
448
<userinput>&COMMANDNAME;</userinput>
453
Run the server in debug mode, read configuration files from
454
the <filename>~/mandos</filename> directory, and use the
455
Zeroconf service name <quote>Test</quote> to not collide with
456
any other official Mandos server on this host:
460
<!-- do not wrap this line -->
461
<userinput>&COMMANDNAME; --debug --configdir ~/mandos --servicename Test</userinput>
467
Run the server normally, but only listen to one interface and
468
only on the link-local address on that interface:
472
<!-- do not wrap this line -->
473
<userinput>&COMMANDNAME; --interface eth7 --address fe80::aede:48ff:fe71:f6f2</userinput>
384
479
<refsect1 id="security">
385
480
<title>SECURITY</title>
481
<refsect2 id="SERVER">
482
<title>SERVER</title>
484
Running this <command>&COMMANDNAME;</command> server program
485
should not in itself present any security risk to the host
486
computer running it. The program does not need any special
487
privileges to run, and is designed to run as a non-root user.
490
<refsect2 id="CLIENTS">
491
<title>CLIENTS</title>
493
The server only gives out its stored data to clients which
494
does have the OpenPGP key of the stored fingerprint. This is
495
guaranteed by the fact that the client sends its OpenPGP
496
public key in the TLS handshake; this ensures it to be
497
genuine. The server computes the fingerprint of the key
498
itself and looks up the fingerprint in its list of
499
clients. The <filename>clients.conf</filename> file (see
500
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
501
<manvolnum>5</manvolnum></citerefentry>)
502
<emphasis>must</emphasis> be made non-readable by anyone
503
except the user running the server.
506
As detailed in <xref linkend="checking"/>, the status of all
507
client computers will continually be checked and be assumed
508
compromised if they are gone for too long.
511
If a client is compromised, its downtime should be duly noted
512
by the server which would therefore declare the client
513
invalid. But if the server was ever restarted, it would
514
re-read its client list from its configuration file and again
515
regard all clients therein as valid, and hence eligible to
516
receive their passwords. Therefore, be careful when
517
restarting servers if it is suspected that a client has, in
518
fact, been compromised by parties who may now be running a
519
fake Mandos client with the keys from the non-encrypted
520
initial <acronym>RAM</acronym> image of the client host. What
521
should be done in that case (if restarting the server program
522
really is necessary) is to stop the server program, edit the
523
configuration file to omit any suspect clients, and restart
527
For more details on client-side security, see
528
<citerefentry><refentrytitle>password-request</refentrytitle>
529
<manvolnum>8mandos</manvolnum></citerefentry>.
390
534
<refsect1 id="see_also">
391
535
<title>SEE ALSO</title>
392
<itemizedlist spacing="compact">
394
<citerefentry><refentrytitle>password-request</refentrytitle>
395
<manvolnum>8mandos</manvolnum></citerefentry>
399
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
400
<manvolnum>8mandos</manvolnum></citerefentry>
404
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
408
<ulink url="http://www.avahi.org/">Avahi</ulink>
413
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
417
<citation>RFC 4880: <citetitle>OpenPGP Message
418
Format</citetitle></citation>
422
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
423
Transport Layer Security</citetitle></citation>
427
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
428
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
429
Unicast Addresses</citation>
538
<refentrytitle>mandos-clients.conf</refentrytitle>
539
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
540
<refentrytitle>mandos.conf</refentrytitle>
541
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
542
<refentrytitle>password-request</refentrytitle>
543
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
544
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
550
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
554
Zeroconf is the network protocol standard used by clients
555
for finding this Mandos server on the local network.
561
<ulink url="http://www.avahi.org/">Avahi</ulink>
565
Avahi is the library this server calls to implement
566
Zeroconf service announcements.
572
<ulink url="http://www.gnu.org/software/gnutls/"
577
GnuTLS is the library this server uses to implement TLS for
578
communicating securely with the client, and at the same time
579
confidently get the client’s public OpenPGP key.
585
RFC 4291: <citetitle>IP Version 6 Addressing
586
Architecture</citetitle>
591
<term>Section 2.2: <citetitle>Text Representation of
592
Addresses</citetitle></term>
593
<listitem><para/></listitem>
596
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
597
Address</citetitle></term>
598
<listitem><para/></listitem>
601
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
602
Addresses</citetitle></term>
605
The clients use IPv6 link-local addresses, which are
606
immediately usable since a link-local addresses is
607
automatically assigned to a network interfaces when it
617
RFC 4346: <citetitle>The Transport Layer Security (TLS)
618
Protocol Version 1.1</citetitle>
622
TLS 1.1 is the protocol implemented by GnuTLS.
628
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
632
The data sent to clients is binary encrypted OpenPGP data.
638
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
643
This is implemented by GnuTLS and used by this server so
644
that OpenPGP keys can be used.
651
<!-- Local Variables: -->
652
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
653
<!-- time-stamp-end: "[\"']>" -->
654
<!-- time-stamp-format: "%:y-%02m-%02d" -->