1
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">
4
5
<!ENTITY COMMANDNAME "mandos">
5
<!ENTITY TIMESTAMP "2012-06-17">
6
<!ENTITY % common SYSTEM "common.ent">
6
<!ENTITY TIMESTAMP "2008-09-01">
10
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
12
11
<title>Mandos Manual</title>
13
12
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
13
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
14
<productnumber>&VERSION;</productnumber>
16
15
<date>&TIMESTAMP;</date>
19
18
<firstname>Björn</firstname>
20
19
<surname>Påhlsson</surname>
22
<email>belorn@recompile.se</email>
21
<email>belorn@fukt.bsnet.se</email>
26
25
<firstname>Teddy</firstname>
27
26
<surname>Hogeborn</surname>
29
<email>teddy@recompile.se</email>
28
<email>teddy@fukt.bsnet.se</email>
39
34
<holder>Teddy Hogeborn</holder>
40
35
<holder>Björn Påhlsson</holder>
42
37
<xi:include href="legalnotice.xml"/>
46
41
<refentrytitle>&COMMANDNAME;</refentrytitle>
47
42
<manvolnum>8</manvolnum>
88
83
<replaceable>DIRECTORY</replaceable></option></arg>
90
85
<arg><option>--debug</option></arg>
92
<arg><option>--debuglevel
93
<replaceable>LEVEL</replaceable></option></arg>
95
<arg><option>--no-dbus</option></arg>
97
<arg><option>--no-ipv6</option></arg>
99
<arg><option>--no-restore</option></arg>
101
<arg><option>--statedir
102
<replaceable>DIRECTORY</replaceable></option></arg>
104
<arg><option>--socket
105
<replaceable>FD</replaceable></option></arg>
107
<arg><option>--foreground</option></arg>
110
88
<command>&COMMANDNAME;</command>
122
100
<arg choice="plain"><option>--check</option></arg>
124
102
</refsynopsisdiv>
126
104
<refsect1 id="description">
127
105
<title>DESCRIPTION</title>
129
107
<command>&COMMANDNAME;</command> is a server daemon which
130
108
handles incoming request for passwords for a pre-defined list of
131
client host computers. For an introduction, see
132
<citerefentry><refentrytitle>intro</refentrytitle>
133
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
134
uses Zeroconf to announce itself on the local network, and uses
135
TLS to communicate securely with and to authenticate the
136
clients. The Mandos server uses IPv6 to allow Mandos clients to
137
use IPv6 link-local addresses, since the clients will probably
138
not have any other addresses configured (see <xref
139
linkend="overview"/>). Any authenticated client is then given
140
the stored pre-encrypted password for that specific client.
109
client host computers. The Mandos server uses Zeroconf to
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.
144
121
<refsect1 id="purpose">
145
122
<title>PURPOSE</title>
147
125
The purpose of this is to enable <emphasis>remote and unattended
148
126
rebooting</emphasis> of client host computer with an
149
127
<emphasis>encrypted root file system</emphasis>. See <xref
150
128
linkend="overview"/> for details.
154
133
<refsect1 id="options">
155
134
<title>OPTIONS</title>
158
138
<term><option>--help</option></term>
210
190
<xi:include href="mandos-options.xml" xpointer="debug"/>
215
<term><option>--debuglevel
216
<replaceable>LEVEL</replaceable></option></term>
219
Set the debugging log level.
220
<replaceable>LEVEL</replaceable> is a string, one of
221
<quote><literal>CRITICAL</literal></quote>,
222
<quote><literal>ERROR</literal></quote>,
223
<quote><literal>WARNING</literal></quote>,
224
<quote><literal>INFO</literal></quote>, or
225
<quote><literal>DEBUG</literal></quote>, in order of
226
increasing verbosity. The default level is
227
<quote><literal>WARNING</literal></quote>.
233
195
<term><option>--priority <replaceable>
234
196
PRIORITY</replaceable></option></term>
274
<term><option>--no-dbus</option></term>
276
<xi:include href="mandos-options.xml" xpointer="dbus"/>
278
See also <xref linkend="dbus_interface"/>.
284
<term><option>--no-ipv6</option></term>
286
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
291
<term><option>--no-restore</option></term>
293
<xi:include href="mandos-options.xml" xpointer="restore"/>
295
See also <xref linkend="persistent_state"/>.
301
<term><option>--statedir
302
<replaceable>DIRECTORY</replaceable></option></term>
304
<xi:include href="mandos-options.xml" xpointer="statedir"/>
309
<term><option>--socket
310
<replaceable>FD</replaceable></option></term>
312
<xi:include href="mandos-options.xml" xpointer="socket"/>
317
<term><option>--foreground</option></term>
319
<xi:include href="mandos-options.xml"
320
xpointer="foreground"/>
327
237
<refsect1 id="overview">
328
238
<title>OVERVIEW</title>
329
239
<xi:include href="overview.xml"/>
392
302
</tbody></tgroup></table>
395
305
<refsect1 id="checking">
396
306
<title>CHECKING</title>
398
308
The server will, by default, continually check that the clients
399
309
are still up. If a client has not been confirmed as being up
400
310
for some time, the client is assumed to be compromised and is no
401
longer eligible to receive the encrypted password. (Manual
402
intervention is required to re-enable a client.) The timeout,
403
extended timeout, checker program, and interval between checks
404
can be configured both globally and per client; see
405
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
311
longer eligible to receive the encrypted password. The timeout,
312
checker program, and interval between checks can be configured
313
both globally and per client; see <citerefentry>
314
<refentrytitle>mandos-clients.conf</refentrytitle>
406
315
<manvolnum>5</manvolnum></citerefentry>.
410
<refsect1 id="approval">
411
<title>APPROVAL</title>
413
The server can be configured to require manual approval for a
414
client before it is sent its secret. The delay to wait for such
415
approval and the default action (approve or deny) can be
416
configured both globally and per client; see <citerefentry>
417
<refentrytitle>mandos-clients.conf</refentrytitle>
418
<manvolnum>5</manvolnum></citerefentry>. By default all clients
419
will be approved immediately without delay.
422
This can be used to deny a client its secret if not manually
423
approved within a specified time. It can also be used to make
424
the server delay before giving a client its secret, allowing
425
optional manual denying of this specific client.
430
319
<refsect1 id="logging">
431
320
<title>LOGGING</title>
433
322
The server will send log message with various severity levels to
434
<filename class="devicefile">/dev/log</filename>. With the
323
<filename>/dev/log</filename>. With the
435
324
<option>--debug</option> option, it will log even more messages,
436
325
and also show them on the console.
440
<refsect1 id="persistent_state">
441
<title>PERSISTENT STATE</title>
443
Client settings, initially read from
444
<filename>clients.conf</filename>, are persistent across
445
restarts, and run-time changes will override settings in
446
<filename>clients.conf</filename>. However, if a setting is
447
<emphasis>changed</emphasis> (or a client added, or removed) in
448
<filename>clients.conf</filename>, this will take precedence.
452
<refsect1 id="dbus_interface">
453
<title>D-BUS INTERFACE</title>
455
The server will by default provide a D-Bus system bus interface.
456
This interface will only be accessible by the root user or a
457
Mandos-specific user, if such a user exists. For documentation
458
of the D-Bus API, see the file <filename>DBUS-API</filename>.
462
329
<refsect1 id="exit_status">
463
330
<title>EXIT STATUS</title>
519
<term><filename>/var/run/mandos.pid</filename></term>
522
The file containing the process id of the
523
<command>&COMMANDNAME;</command> process started last.
528
<term><filename class="devicefile">/dev/log</filename></term>
532
class="directory">/var/lib/mandos</filename></term>
535
Directory where persistent state will be saved. Change
536
this with the <option>--statedir</option> option. See
537
also the <option>--no-restore</option> option.
386
<term><filename>/var/run/mandos/mandos.pid</filename></term>
389
The file containing the process id of
390
<command>&COMMANDNAME;</command>.
568
421
backtrace. This could be considered a feature.
424
Currently, if a client is declared <quote>invalid</quote> due to
425
having timed out, the server does not record this fact onto
426
permanent storage. This has some security implications, see
427
<xref linkend="CLIENTS"/>.
430
There is currently no way of querying the server of the current
431
status of clients, other than analyzing its <systemitem
432
class="service">syslog</systemitem> output.
571
435
There is no fine-grained control over logging and debug output.
574
This server does not check the expire time of clients’ OpenPGP
438
Debug mode is conflated with running in the foreground.
441
The console log messages does not show a timestamp.
589
455
<informalexample>
591
457
Run the server in debug mode, read configuration files from
592
the <filename class="directory">~/mandos</filename> directory,
593
and use the Zeroconf service name <quote>Test</quote> to not
594
collide with any other official Mandos server on this host:
458
the <filename>~/mandos</filename> directory, and use the
459
Zeroconf service name <quote>Test</quote> to not collide with
460
any other official Mandos server on this host:
646
512
compromised if they are gone for too long.
515
If a client is compromised, its downtime should be duly noted
516
by the server which would therefore declare the client
517
invalid. But if the server was ever restarted, it would
518
re-read its client list from its configuration file and again
519
regard all clients therein as valid, and hence eligible to
520
receive their passwords. Therefore, be careful when
521
restarting servers if it is suspected that a client has, in
522
fact, been compromised by parties who may now be running a
523
fake Mandos client with the keys from the non-encrypted
524
initial <acronym>RAM</acronym> image of the client host. What
525
should be done in that case (if restarting the server program
526
really is necessary) is to stop the server program, edit the
527
configuration file to omit any suspect clients, and restart
649
531
For more details on client-side security, see
650
<citerefentry><refentrytitle>mandos-client</refentrytitle>
532
<citerefentry><refentrytitle>password-request</refentrytitle>
651
533
<manvolnum>8mandos</manvolnum></citerefentry>.
656
538
<refsect1 id="see_also">
657
539
<title>SEE ALSO</title>
659
<citerefentry><refentrytitle>intro</refentrytitle>
660
<manvolnum>8mandos</manvolnum></citerefentry>,
661
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
662
<manvolnum>5</manvolnum></citerefentry>,
663
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
664
<manvolnum>5</manvolnum></citerefentry>,
665
<citerefentry><refentrytitle>mandos-client</refentrytitle>
666
<manvolnum>8mandos</manvolnum></citerefentry>,
667
<citerefentry><refentrytitle>sh</refentrytitle>
668
<manvolnum>1</manvolnum></citerefentry>
542
<refentrytitle>mandos-clients.conf</refentrytitle>
543
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
544
<refentrytitle>mandos.conf</refentrytitle>
545
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
546
<refentrytitle>password-request</refentrytitle>
547
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
548
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>