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">
5
4
<!ENTITY COMMANDNAME "mandos">
6
<!ENTITY TIMESTAMP "2008-08-31">
5
<!ENTITY TIMESTAMP "2011-10-03">
6
<!ENTITY % common SYSTEM "common.ent">
9
10
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
11
12
<title>Mandos Manual</title>
12
13
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
13
14
<productname>Mandos</productname>
14
<productnumber>&VERSION;</productnumber>
15
<productnumber>&version;</productnumber>
15
16
<date>&TIMESTAMP;</date>
18
19
<firstname>Björn</firstname>
19
20
<surname>Påhlsson</surname>
21
<email>belorn@fukt.bsnet.se</email>
22
<email>belorn@recompile.se</email>
25
26
<firstname>Teddy</firstname>
26
27
<surname>Hogeborn</surname>
28
<email>teddy@fukt.bsnet.se</email>
29
<email>teddy@recompile.se</email>
34
38
<holder>Teddy Hogeborn</holder>
35
39
<holder>Björn Påhlsson</holder>
39
This manual page is free software: you can redistribute it
40
and/or modify it under the terms of the GNU General Public
41
License as published by the Free Software Foundation,
42
either version 3 of the License, or (at your option) any
47
This manual page is distributed in the hope that it will
48
be useful, but WITHOUT ANY WARRANTY; without even the
49
implied warranty of MERCHANTABILITY or FITNESS FOR A
50
PARTICULAR PURPOSE. See the GNU General Public License
55
You should have received a copy of the GNU General Public
56
License along with this program; If not, see
57
<ulink url="http://www.gnu.org/licenses/"/>.
41
<xi:include href="legalnotice.xml"/>
63
45
<refentrytitle>&COMMANDNAME;</refentrytitle>
64
46
<manvolnum>8</manvolnum>
122
111
<arg choice="plain"><option>--check</option></arg>
124
113
</refsynopsisdiv>
126
115
<refsect1 id="description">
127
116
<title>DESCRIPTION</title>
129
118
<command>&COMMANDNAME;</command> is a server daemon which
130
119
handles incoming request for passwords for a pre-defined list of
131
client host computers. The Mandos server uses Zeroconf to
132
announce itself on the local network, and uses TLS to
133
communicate securely with and to authenticate the clients. The
134
Mandos server uses IPv6 to allow Mandos clients to use IPv6
135
link-local addresses, since the clients will probably not have
136
any other addresses configured (see <xref linkend="overview"/>).
137
Any authenticated client is then given the stored pre-encrypted
138
password for that specific client.
120
client host computers. For an introduction, see
121
<citerefentry><refentrytitle>intro</refentrytitle>
122
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
123
uses Zeroconf to announce itself on the local network, and uses
124
TLS to communicate securely with and to authenticate the
125
clients. The Mandos server uses IPv6 to allow Mandos clients to
126
use IPv6 link-local addresses, since the clients will probably
127
not have any other addresses configured (see <xref
128
linkend="overview"/>). Any authenticated client is then given
129
the stored pre-encrypted password for that specific client.
143
133
<refsect1 id="purpose">
144
134
<title>PURPOSE</title>
147
136
The purpose of this is to enable <emphasis>remote and unattended
148
137
rebooting</emphasis> of client host computer with an
149
138
<emphasis>encrypted root file system</emphasis>. See <xref
150
139
linkend="overview"/> for details.
155
143
<refsect1 id="options">
156
144
<title>OPTIONS</title>
147
<term><option>--help</option></term>
160
148
<term><option>-h</option></term>
161
<term><option>--help</option></term>
164
151
Show a help message and exit
157
<term><option>--interface</option>
158
<replaceable>NAME</replaceable></term>
170
159
<term><option>-i</option>
171
160
<replaceable>NAME</replaceable></term>
172
<term><option>--interface</option>
173
<replaceable>NAME</replaceable></term>
175
162
<xi:include href="mandos-options.xml" xpointer="interface"/>
180
<term><literal>-a</literal>, <literal>--address <replaceable>
181
ADDRESS</replaceable></literal></term>
167
<term><option>--address
168
<replaceable>ADDRESS</replaceable></option></term>
170
<replaceable>ADDRESS</replaceable></option></term>
183
172
<xi:include href="mandos-options.xml" xpointer="address"/>
188
<term><literal>-p</literal>, <literal>--port <replaceable>
189
PORT</replaceable></literal></term>
178
<replaceable>PORT</replaceable></option></term>
180
<replaceable>PORT</replaceable></option></term>
191
182
<xi:include href="mandos-options.xml" xpointer="port"/>
196
<term><literal>--check</literal></term>
187
<term><option>--check</option></term>
199
190
Run the server’s self-tests. This includes any unit
206
<term><literal>--debug</literal></term>
197
<term><option>--debug</option></term>
208
199
<xi:include href="mandos-options.xml" xpointer="debug"/>
213
<term><literal>--priority <replaceable>
214
PRIORITY</replaceable></literal></term>
204
<term><option>--debuglevel
205
<replaceable>LEVEL</replaceable></option></term>
208
Set the debugging log level.
209
<replaceable>LEVEL</replaceable> is a string, one of
210
<quote><literal>CRITICAL</literal></quote>,
211
<quote><literal>ERROR</literal></quote>,
212
<quote><literal>WARNING</literal></quote>,
213
<quote><literal>INFO</literal></quote>, or
214
<quote><literal>DEBUG</literal></quote>, in order of
215
increasing verbosity. The default level is
216
<quote><literal>WARNING</literal></quote>.
222
<term><option>--priority <replaceable>
223
PRIORITY</replaceable></option></term>
216
225
<xi:include href="mandos-options.xml" xpointer="priority"/>
221
<term><literal>--servicename <replaceable>NAME</replaceable>
230
<term><option>--servicename
231
<replaceable>NAME</replaceable></option></term>
224
233
<xi:include href="mandos-options.xml"
225
234
xpointer="servicename"/>
230
<term><literal>--configdir <replaceable>DIR</replaceable>
239
<term><option>--configdir
240
<replaceable>DIRECTORY</replaceable></option></term>
234
243
Directory to search for configuration files. Default is
245
<term><literal>--version</literal></term>
254
<term><option>--version</option></term>
248
257
Prints the program version and exit.
263
<term><option>--no-dbus</option></term>
265
<xi:include href="mandos-options.xml" xpointer="dbus"/>
267
See also <xref linkend="dbus_interface"/>.
273
<term><option>--no-ipv6</option></term>
275
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
255
281
<refsect1 id="overview">
256
282
<title>OVERVIEW</title>
257
283
<xi:include href="overview.xml"/>
259
285
This program is the server part. It is a normal server program
260
286
and will run in a normal system environment, not in an initial
261
RAM disk environment.
287
<acronym>RAM</acronym> disk environment.
265
291
<refsect1 id="protocol">
266
292
<title>NETWORK PROTOCOL</title>
320
346
</tbody></tgroup></table>
323
349
<refsect1 id="checking">
324
350
<title>CHECKING</title>
326
352
The server will, by default, continually check that the clients
327
353
are still up. If a client has not been confirmed as being up
328
354
for some time, the client is assumed to be compromised and is no
329
longer eligible to receive the encrypted password. The timeout,
330
checker program, and interval between checks can be configured
331
both globally and per client; see <citerefentry>
355
longer eligible to receive the encrypted password. (Manual
356
intervention is required to re-enable a client.) The timeout,
357
extended timeout, checker program, and interval between checks
358
can be configured both globally and per client; see
359
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
360
<manvolnum>5</manvolnum></citerefentry>. A client successfully
361
receiving its password will also be treated as a successful
366
<refsect1 id="approval">
367
<title>APPROVAL</title>
369
The server can be configured to require manual approval for a
370
client before it is sent its secret. The delay to wait for such
371
approval and the default action (approve or deny) can be
372
configured both globally and per client; see <citerefentry>
332
373
<refentrytitle>mandos-clients.conf</refentrytitle>
333
<manvolnum>5</manvolnum></citerefentry>.
374
<manvolnum>5</manvolnum></citerefentry>. By default all clients
375
will be approved immediately without delay.
378
This can be used to deny a client its secret if not manually
379
approved within a specified time. It can also be used to make
380
the server delay before giving a client its secret, allowing
381
optional manual denying of this specific client.
337
386
<refsect1 id="logging">
338
387
<title>LOGGING</title>
343
392
and also show them on the console.
396
<refsect1 id="dbus_interface">
397
<title>D-BUS INTERFACE</title>
399
The server will by default provide a D-Bus system bus interface.
400
This interface will only be accessible by the root user or a
401
Mandos-specific user, if such a user exists. For documentation
402
of the D-Bus API, see the file <filename>DBUS-API</filename>.
347
406
<refsect1 id="exit_status">
348
407
<title>EXIT STATUS</title>
439
498
backtrace. This could be considered a feature.
442
Currently, if a client is declared <quote>invalid</quote> due to
443
having timed out, the server does not record this fact onto
444
permanent storage. This has some security implications, see
445
<xref linkend="CLIENTS"/>.
448
There is currently no way of querying the server of the current
449
status of clients, other than analyzing its <systemitem
450
class="service">syslog</systemitem> output.
501
Currently, if a client is disabled due to having timed out, the
502
server does not record this fact onto permanent storage. This
503
has some security implications, see <xref linkend="clients"/>.
453
506
There is no fine-grained control over logging and debug output.
533
590
If a client is compromised, its downtime should be duly noted
534
by the server which would therefore declare the client
535
invalid. But if the server was ever restarted, it would
536
re-read its client list from its configuration file and again
537
regard all clients therein as valid, and hence eligible to
538
receive their passwords. Therefore, be careful when
539
restarting servers if it is suspected that a client has, in
540
fact, been compromised by parties who may now be running a
541
fake Mandos client with the keys from the non-encrypted
542
initial RAM image of the client host. What should be done in
543
that case (if restarting the server program really is
544
necessary) is to stop the server program, edit the
545
configuration file to omit any suspect clients, and restart
591
by the server which would therefore disable the client. But
592
if the server was ever restarted, it would re-read its client
593
list from its configuration file and again regard all clients
594
therein as enabled, and hence eligible to receive their
595
passwords. Therefore, be careful when restarting servers if
596
it is suspected that a client has, in fact, been compromised
597
by parties who may now be running a fake Mandos client with
598
the keys from the non-encrypted initial <acronym>RAM</acronym>
599
image of the client host. What should be done in that case
600
(if restarting the server program really is necessary) is to
601
stop the server program, edit the configuration file to omit
602
any suspect clients, and restart the server program.
549
605
For more details on client-side security, see
550
<citerefentry><refentrytitle>password-request</refentrytitle>
606
<citerefentry><refentrytitle>mandos-client</refentrytitle>
551
607
<manvolnum>8mandos</manvolnum></citerefentry>.
556
612
<refsect1 id="see_also">
557
613
<title>SEE ALSO</title>
560
<refentrytitle>mandos-clients.conf</refentrytitle>
561
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
562
<refentrytitle>mandos.conf</refentrytitle>
563
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
564
<refentrytitle>password-request</refentrytitle>
565
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
566
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
615
<citerefentry><refentrytitle>intro</refentrytitle>
616
<manvolnum>8mandos</manvolnum></citerefentry>,
617
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
618
<manvolnum>5</manvolnum></citerefentry>,
619
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
620
<manvolnum>5</manvolnum></citerefentry>,
621
<citerefentry><refentrytitle>mandos-client</refentrytitle>
622
<manvolnum>8mandos</manvolnum></citerefentry>,
623
<citerefentry><refentrytitle>sh</refentrytitle>
624
<manvolnum>1</manvolnum></citerefentry>