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 "2018-02-08">
6
<!ENTITY % common SYSTEM "common.ent">
6
<!ENTITY OVERVIEW SYSTEM "overview.xml">
10
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
12
<title>Mandos Manual</title>
11
<title>&COMMANDNAME;</title>
13
12
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
16
<date>&TIMESTAMP;</date>
13
<productname>&COMMANDNAME;</productname>
14
<productnumber>&VERSION;</productnumber>
19
17
<firstname>Björn</firstname>
20
18
<surname>Påhlsson</surname>
22
<email>belorn@recompile.se</email>
20
<email>belorn@fukt.bsnet.se</email>
26
24
<firstname>Teddy</firstname>
27
25
<surname>Hogeborn</surname>
29
<email>teddy@recompile.se</email>
27
<email>teddy@fukt.bsnet.se</email>
45
33
<holder>Teddy Hogeborn</holder>
46
34
<holder>Björn Påhlsson</holder>
48
<xi:include href="legalnotice.xml"/>
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
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
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/"/>.
52
62
<refentrytitle>&COMMANDNAME;</refentrytitle>
53
63
<manvolnum>8</manvolnum>
57
67
<refname><command>&COMMANDNAME;</command></refname>
59
Gives encrypted passwords to authenticated Mandos clients
69
Sends encrypted passwords to authenticated Mandos clients
65
75
<command>&COMMANDNAME;</command>
67
<arg choice="plain"><option>--interface
68
<replaceable>NAME</replaceable></option></arg>
69
<arg choice="plain"><option>-i
70
<replaceable>NAME</replaceable></option></arg>
74
<arg choice="plain"><option>--address
75
<replaceable>ADDRESS</replaceable></option></arg>
76
<arg choice="plain"><option>-a
77
<replaceable>ADDRESS</replaceable></option></arg>
81
<arg choice="plain"><option>--port
82
<replaceable>PORT</replaceable></option></arg>
83
<arg choice="plain"><option>-p
84
<replaceable>PORT</replaceable></option></arg>
87
<arg><option>--priority
88
<replaceable>PRIORITY</replaceable></option></arg>
90
<arg><option>--servicename
91
<replaceable>NAME</replaceable></option></arg>
93
<arg><option>--configdir
94
<replaceable>DIRECTORY</replaceable></option></arg>
96
<arg><option>--debug</option></arg>
98
<arg><option>--debuglevel
99
<replaceable>LEVEL</replaceable></option></arg>
101
<arg><option>--no-dbus</option></arg>
103
<arg><option>--no-ipv6</option></arg>
105
<arg><option>--no-restore</option></arg>
107
<arg><option>--statedir
108
<replaceable>DIRECTORY</replaceable></option></arg>
110
<arg><option>--socket
111
<replaceable>FD</replaceable></option></arg>
113
<arg><option>--foreground</option></arg>
115
<arg><option>--no-zeroconf</option></arg>
76
<arg>--interface<arg choice="plain">IF</arg></arg>
77
<arg>--address<arg choice="plain">ADDRESS</arg></arg>
78
<arg>--port<arg choice="plain">PORT</arg></arg>
79
<arg>--priority<arg choice="plain">PRIORITY</arg></arg>
80
<arg>--servicename<arg choice="plain">NAME</arg></arg>
81
<arg>--configdir<arg choice="plain">DIRECTORY</arg></arg>
85
<command>&COMMANDNAME;</command>
86
<arg>-i<arg choice="plain">IF</arg></arg>
87
<arg>-a<arg choice="plain">ADDRESS</arg></arg>
88
<arg>-p<arg choice="plain">PORT</arg></arg>
89
<arg>--priority<arg choice="plain">PRIORITY</arg></arg>
90
<arg>--servicename<arg choice="plain">NAME</arg></arg>
91
<arg>--configdir<arg choice="plain">DIRECTORY</arg></arg>
118
95
<command>&COMMANDNAME;</command>
119
96
<group choice="req">
120
<arg choice="plain"><option>--help</option></arg>
121
<arg choice="plain"><option>-h</option></arg>
97
<arg choice="plain">-h</arg>
98
<arg choice="plain">--help</arg>
125
102
<command>&COMMANDNAME;</command>
126
<arg choice="plain"><option>--version</option></arg>
103
<arg choice="plain">--version</arg>
129
106
<command>&COMMANDNAME;</command>
130
<arg choice="plain"><option>--check</option></arg>
107
<arg choice="plain">--check</arg>
132
109
</refsynopsisdiv>
134
111
<refsect1 id="description">
135
112
<title>DESCRIPTION</title>
137
114
<command>&COMMANDNAME;</command> is a server daemon which
138
115
handles incoming request for passwords for a pre-defined list of
139
client host computers. For an introduction, see
140
<citerefentry><refentrytitle>intro</refentrytitle>
141
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
142
uses Zeroconf to announce itself on the local network, and uses
143
TLS to communicate securely with and to authenticate the
144
clients. The Mandos server uses IPv6 to allow Mandos clients to
145
use IPv6 link-local addresses, since the clients will probably
146
not have any other addresses configured (see <xref
147
linkend="overview"/>). Any authenticated client is then given
148
the stored pre-encrypted password for that specific client.
116
client host computers. The Mandos server uses Zeroconf to
117
announce itself on the local network, and uses TLS to
118
communicate securely with and to authenticate the clients. The
119
Mandos server uses IPv6 to allow Mandos clients to use IPv6
120
link-local addresses, since the clients will probably not have
121
any other addresses configured (see <xref linkend="overview"/>).
122
Any authenticated client is then given the stored pre-encrypted
123
password for that specific client.
152
128
<refsect1 id="purpose">
153
129
<title>PURPOSE</title>
155
132
The purpose of this is to enable <emphasis>remote and unattended
156
133
rebooting</emphasis> of client host computer with an
157
134
<emphasis>encrypted root file system</emphasis>. See <xref
158
135
linkend="overview"/> for details.
162
140
<refsect1 id="options">
163
141
<title>OPTIONS</title>
166
<term><option>--help</option></term>
167
<term><option>-h</option></term>
145
<term><literal>-h</literal>, <literal>--help</literal></term>
170
148
Show a help message and exit
176
<term><option>--interface</option>
177
<replaceable>NAME</replaceable></term>
178
<term><option>-i</option>
179
<replaceable>NAME</replaceable></term>
181
<xi:include href="mandos-options.xml" xpointer="interface"/>
186
<term><option>--address
187
<replaceable>ADDRESS</replaceable></option></term>
189
<replaceable>ADDRESS</replaceable></option></term>
191
<xi:include href="mandos-options.xml" xpointer="address"/>
197
<replaceable>PORT</replaceable></option></term>
199
<replaceable>PORT</replaceable></option></term>
201
<xi:include href="mandos-options.xml" xpointer="port"/>
206
<term><option>--check</option></term>
154
<term><literal>-i</literal>, <literal>--interface <replaceable>
155
IF</replaceable></literal></term>
158
Only announce the server and listen to requests on network
159
interface <replaceable>IF</replaceable>. Default is to
160
use all available interfaces. <emphasis>Note:</emphasis>
161
a failure to bind to the specified interface is not
162
considered critical, and the server does not exit.
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
<quote><literal>::FFFF:192.0.2.3</literal></quote> syntax.
176
Also, if a link-local address is specified, an interface
177
should be set, since a link-local address is only valid on
178
a single interface. By default, the server will listen to
179
all available addresses.
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>
209
200
Run the server’s self-tests. This includes any unit
216
<term><option>--debug</option></term>
218
<xi:include href="mandos-options.xml" xpointer="debug"/>
223
<term><option>--debuglevel
224
<replaceable>LEVEL</replaceable></option></term>
227
Set the debugging log level.
228
<replaceable>LEVEL</replaceable> is a string, one of
229
<quote><literal>CRITICAL</literal></quote>,
230
<quote><literal>ERROR</literal></quote>,
231
<quote><literal>WARNING</literal></quote>,
232
<quote><literal>INFO</literal></quote>, or
233
<quote><literal>DEBUG</literal></quote>, in order of
234
increasing verbosity. The default level is
235
<quote><literal>WARNING</literal></quote>.
241
<term><option>--priority <replaceable>
242
PRIORITY</replaceable></option></term>
244
<xi:include href="mandos-options.xml" xpointer="priority"/>
249
<term><option>--servicename
250
<replaceable>NAME</replaceable></option></term>
252
<xi:include href="mandos-options.xml"
253
xpointer="servicename"/>
258
<term><option>--configdir
259
<replaceable>DIRECTORY</replaceable></option></term>
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
223
clients. The default is
224
<quote><literal>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal></quote>.
225
See <citerefentry><refentrytitle>gnutls_priority_init
226
</refentrytitle><manvolnum>3</manvolnum></citerefentry>
227
for the syntax. <emphasis>Warning</emphasis>: changing
228
this may make the TLS handshake fail, making communication
229
with clients impossible.
235
<term><literal>--servicename <replaceable>NAME</replaceable>
239
Zeroconf service name. The default is
240
<quote><literal>Mandos</literal></quote>. This only needs
241
to be changed this if it, for some reason, is necessary to
242
run more than one server on the same
243
<emphasis>host</emphasis>, which would not normally be
244
useful. If there are name collisions on the same
245
<emphasis>network</emphasis>, the newer server will
246
automatically rename itself to <quote><literal>Mandos
247
#2</literal></quote>, and so on; therefore, this option is
248
not needed in that case.
254
<term><literal>--configdir <replaceable>DIR</replaceable>
262
258
Directory to search for configuration files. Default is
273
<term><option>--version</option></term>
269
<term><literal>--version</literal></term>
276
272
Prints the program version and exit.
282
<term><option>--no-dbus</option></term>
284
<xi:include href="mandos-options.xml" xpointer="dbus"/>
286
See also <xref linkend="dbus_interface"/>.
292
<term><option>--no-ipv6</option></term>
294
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
299
<term><option>--no-restore</option></term>
301
<xi:include href="mandos-options.xml" xpointer="restore"/>
303
See also <xref linkend="persistent_state"/>.
309
<term><option>--statedir
310
<replaceable>DIRECTORY</replaceable></option></term>
312
<xi:include href="mandos-options.xml" xpointer="statedir"/>
317
<term><option>--socket
318
<replaceable>FD</replaceable></option></term>
320
<xi:include href="mandos-options.xml" xpointer="socket"/>
325
<term><option>--foreground</option></term>
327
<xi:include href="mandos-options.xml"
328
xpointer="foreground"/>
333
<term><option>--no-zeroconf</option></term>
335
<xi:include href="mandos-options.xml" xpointer="zeroconf"/>
342
279
<refsect1 id="overview">
343
280
<title>OVERVIEW</title>
344
<xi:include href="overview.xml"/>
346
283
This program is the server part. It is a normal server program
347
284
and will run in a normal system environment, not in an initial
348
<acronym>RAM</acronym> disk environment.
285
RAM disk environment.
352
289
<refsect1 id="protocol">
353
290
<title>NETWORK PROTOCOL</title>
407
344
</tbody></tgroup></table>
410
347
<refsect1 id="checking">
411
348
<title>CHECKING</title>
413
350
The server will, by default, continually check that the clients
414
351
are still up. If a client has not been confirmed as being up
415
352
for some time, the client is assumed to be compromised and is no
416
longer eligible to receive the encrypted password. (Manual
417
intervention is required to re-enable a client.) The timeout,
418
extended timeout, checker program, and interval between checks
419
can be configured both globally and per client; see
420
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
353
longer eligible to receive the encrypted password. The timeout,
354
checker program, and interval between checks can be configured
355
both globally and per client; see <citerefentry>
356
<refentrytitle>mandos.conf</refentrytitle>
357
<manvolnum>5</manvolnum></citerefentry> and <citerefentry>
358
<refentrytitle>mandos-clients.conf</refentrytitle>
421
359
<manvolnum>5</manvolnum></citerefentry>.
425
<refsect1 id="approval">
426
<title>APPROVAL</title>
428
The server can be configured to require manual approval for a
429
client before it is sent its secret. The delay to wait for such
430
approval and the default action (approve or deny) can be
431
configured both globally and per client; see <citerefentry>
432
<refentrytitle>mandos-clients.conf</refentrytitle>
433
<manvolnum>5</manvolnum></citerefentry>. By default all clients
434
will be approved immediately without delay.
437
This can be used to deny a client its secret if not manually
438
approved within a specified time. It can also be used to make
439
the server delay before giving a client its secret, allowing
440
optional manual denying of this specific client.
445
363
<refsect1 id="logging">
446
364
<title>LOGGING</title>
448
The server will send log message with various severity levels to
449
<filename class="devicefile">/dev/log</filename>. With the
366
The server will send log messaged with various severity levels
367
to <filename>/dev/log</filename>. With the
450
368
<option>--debug</option> option, it will log even more messages,
451
369
and also show them on the console.
455
<refsect1 id="persistent_state">
456
<title>PERSISTENT STATE</title>
458
Client settings, initially read from
459
<filename>clients.conf</filename>, are persistent across
460
restarts, and run-time changes will override settings in
461
<filename>clients.conf</filename>. However, if a setting is
462
<emphasis>changed</emphasis> (or a client added, or removed) in
463
<filename>clients.conf</filename>, this will take precedence.
467
<refsect1 id="dbus_interface">
468
<title>D-BUS INTERFACE</title>
470
The server will by default provide a D-Bus system bus interface.
471
This interface will only be accessible by the root user or a
472
Mandos-specific user, if such a user exists. For documentation
473
of the D-Bus API, see the file <filename>DBUS-API</filename>.
477
373
<refsect1 id="exit_status">
478
374
<title>EXIT STATUS</title>
663
556
compromised if they are gone for too long.
559
If a client is compromised, its downtime should be duly noted
560
by the server which would therefore declare the client
561
invalid. But if the server was ever restarted, it would
562
re-read its client list from its configuration file and again
563
regard all clients therein as valid, and hence eligible to
564
receive their passwords. Therefore, be careful when
565
restarting servers if it is suspected that a client has, in
566
fact, been compromised by parties who may now be running a
567
fake Mandos client with the keys from the non-encrypted
568
initial RAM image of the client host. What should be done in
569
that case (if restarting the server program really is
570
necessary) is to stop the server program, edit the
571
configuration file to omit any suspect clients, and restart
666
575
For more details on client-side security, see
667
<citerefentry><refentrytitle>mandos-client</refentrytitle>
576
<citerefentry><refentrytitle>password-request</refentrytitle>
668
577
<manvolnum>8mandos</manvolnum></citerefentry>.
673
582
<refsect1 id="see_also">
674
583
<title>SEE ALSO</title>
676
<citerefentry><refentrytitle>intro</refentrytitle>
677
<manvolnum>8mandos</manvolnum></citerefentry>,
678
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
679
<manvolnum>5</manvolnum></citerefentry>,
680
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
681
<manvolnum>5</manvolnum></citerefentry>,
682
<citerefentry><refentrytitle>mandos-client</refentrytitle>
683
<manvolnum>8mandos</manvolnum></citerefentry>,
684
<citerefentry><refentrytitle>sh</refentrytitle>
685
<manvolnum>1</manvolnum></citerefentry>
588
<refentrytitle>password-request</refentrytitle>
589
<manvolnum>8mandos</manvolnum>
594
This is the actual program which talks to this server.
595
Note that it is normally not invoked directly, and is only
596
run in the initial RAM disk environment, and not on a
597
fully started system.
690
603
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
724
RFC 4291: <citetitle>IP Version 6 Addressing
725
Architecture</citetitle>
638
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
639
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
640
Unicast Addresses</citation>
730
<term>Section 2.2: <citetitle>Text Representation of
731
Addresses</citetitle></term>
732
<listitem><para/></listitem>
735
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
736
Address</citetitle></term>
737
<listitem><para/></listitem>
740
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
741
Addresses</citetitle></term>
744
The clients use IPv6 link-local addresses, which are
745
immediately usable since a link-local addresses is
746
automatically assigned to a network interfaces when it
644
The clients use IPv6 link-local addresses, which are
645
immediately usable since a link-local addresses is
646
automatically assigned to a network interfaces when it is
756
RFC 5246: <citetitle>The Transport Layer Security (TLS)
757
Protocol Version 1.2</citetitle>
653
<citation>RFC 4346: <citetitle>The Transport Layer Security
654
(TLS) Protocol Version 1.1</citetitle></citation>
761
TLS 1.2 is the protocol implemented by GnuTLS.
658
TLS 1.1 is the protocol implemented by GnuTLS.
767
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
664
<citation>RFC 4880: <citetitle>OpenPGP Message
665
Format</citetitle></citation>