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 "2010-09-25">
6
<!ENTITY % common SYSTEM "common.ent">
6
<!ENTITY TIMESTAMP "2008-08-30">
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>
36
34
<holder>Teddy Hogeborn</holder>
37
35
<holder>Björn Påhlsson</holder>
39
<xi:include href="legalnotice.xml"/>
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/"/>.
43
63
<refentrytitle>&COMMANDNAME;</refentrytitle>
44
64
<manvolnum>8</manvolnum>
50
70
Gives encrypted passwords to authenticated Mandos clients
56
76
<command>&COMMANDNAME;</command>
58
<arg choice="plain"><option>--interface
59
<replaceable>NAME</replaceable></option></arg>
60
<arg choice="plain"><option>-i
61
<replaceable>NAME</replaceable></option></arg>
65
<arg choice="plain"><option>--address
66
<replaceable>ADDRESS</replaceable></option></arg>
67
<arg choice="plain"><option>-a
68
<replaceable>ADDRESS</replaceable></option></arg>
72
<arg choice="plain"><option>--port
73
<replaceable>PORT</replaceable></option></arg>
74
<arg choice="plain"><option>-p
75
<replaceable>PORT</replaceable></option></arg>
78
<arg><option>--priority
79
<replaceable>PRIORITY</replaceable></option></arg>
81
<arg><option>--servicename
82
<replaceable>NAME</replaceable></option></arg>
84
<arg><option>--configdir
85
<replaceable>DIRECTORY</replaceable></option></arg>
87
<arg><option>--debug</option></arg>
89
<arg><option>--no-dbus</option></arg>
91
<arg><option>--no-ipv6</option></arg>
77
<arg>--interface<arg choice="plain">NAME</arg></arg>
78
<arg>--address<arg choice="plain">ADDRESS</arg></arg>
79
<arg>--port<arg choice="plain">PORT</arg></arg>
80
<arg>--priority<arg choice="plain">PRIORITY</arg></arg>
81
<arg>--servicename<arg choice="plain">NAME</arg></arg>
82
<arg>--configdir<arg choice="plain">DIRECTORY</arg></arg>
86
<command>&COMMANDNAME;</command>
87
<arg>-i<arg choice="plain">NAME</arg></arg>
88
<arg>-a<arg choice="plain">ADDRESS</arg></arg>
89
<arg>-p<arg choice="plain">PORT</arg></arg>
90
<arg>--priority<arg choice="plain">PRIORITY</arg></arg>
91
<arg>--servicename<arg choice="plain">NAME</arg></arg>
92
<arg>--configdir<arg choice="plain">DIRECTORY</arg></arg>
94
96
<command>&COMMANDNAME;</command>
95
97
<group choice="req">
96
<arg choice="plain"><option>--help</option></arg>
97
<arg choice="plain"><option>-h</option></arg>
98
<arg choice="plain">-h</arg>
99
<arg choice="plain">--help</arg>
101
103
<command>&COMMANDNAME;</command>
102
<arg choice="plain"><option>--version</option></arg>
104
<arg choice="plain">--version</arg>
105
107
<command>&COMMANDNAME;</command>
106
<arg choice="plain"><option>--check</option></arg>
108
<arg choice="plain">--check</arg>
108
110
</refsynopsisdiv>
110
112
<refsect1 id="description">
111
113
<title>DESCRIPTION</title>
121
123
Any authenticated client is then given the stored pre-encrypted
122
124
password for that specific client.
126
129
<refsect1 id="purpose">
127
130
<title>PURPOSE</title>
129
133
The purpose of this is to enable <emphasis>remote and unattended
130
134
rebooting</emphasis> of client host computer with an
131
135
<emphasis>encrypted root file system</emphasis>. See <xref
132
136
linkend="overview"/> for details.
136
141
<refsect1 id="options">
137
142
<title>OPTIONS</title>
146
<term><option>-h</option></term>
140
147
<term><option>--help</option></term>
141
<term><option>-h</option></term>
144
150
Show a help message and exit
156
<term><option>-i</option>
157
<replaceable>NAME</replaceable></term>
150
158
<term><option>--interface</option>
151
159
<replaceable>NAME</replaceable></term>
152
<term><option>-i</option>
153
<replaceable>NAME</replaceable></term>
155
161
<xi:include href="mandos-options.xml" xpointer="interface"/>
160
<term><option>--address
161
<replaceable>ADDRESS</replaceable></option></term>
163
<replaceable>ADDRESS</replaceable></option></term>
166
<term><literal>-a</literal>, <literal>--address <replaceable>
167
ADDRESS</replaceable></literal></term>
165
169
<xi:include href="mandos-options.xml" xpointer="address"/>
171
<replaceable>PORT</replaceable></option></term>
173
<replaceable>PORT</replaceable></option></term>
174
<term><literal>-p</literal>, <literal>--port <replaceable>
175
PORT</replaceable></literal></term>
175
177
<xi:include href="mandos-options.xml" xpointer="port"/>
180
<term><option>--check</option></term>
182
<term><literal>--check</literal></term>
183
185
Run the server’s self-tests. This includes any unit
190
<term><option>--debug</option></term>
192
<term><literal>--debug</literal></term>
192
194
<xi:include href="mandos-options.xml" xpointer="debug"/>
197
<term><option>--priority <replaceable>
198
PRIORITY</replaceable></option></term>
199
<term><literal>--priority <replaceable>
200
PRIORITY</replaceable></literal></term>
200
202
<xi:include href="mandos-options.xml" xpointer="priority"/>
205
<term><option>--servicename
206
<replaceable>NAME</replaceable></option></term>
207
<term><literal>--servicename <replaceable>NAME</replaceable>
208
210
<xi:include href="mandos-options.xml"
209
211
xpointer="servicename"/>
214
<term><option>--configdir
215
<replaceable>DIRECTORY</replaceable></option></term>
216
<term><literal>--configdir <replaceable>DIR</replaceable>
218
220
Directory to search for configuration files. Default is
229
<term><option>--version</option></term>
231
<term><literal>--version</literal></term>
232
234
Prints the program version and exit.
238
<term><option>--no-dbus</option></term>
240
<xi:include href="mandos-options.xml" xpointer="dbus"/>
242
See also <xref linkend="dbus_interface"/>.
248
<term><option>--no-ipv6</option></term>
250
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
256
241
<refsect1 id="overview">
257
242
<title>OVERVIEW</title>
258
243
<xi:include href="overview.xml"/>
260
245
This program is the server part. It is a normal server program
261
246
and will run in a normal system environment, not in an initial
262
<acronym>RAM</acronym> disk environment.
247
RAM disk environment.
266
251
<refsect1 id="protocol">
267
252
<title>NETWORK PROTOCOL</title>
321
306
</tbody></tgroup></table>
324
309
<refsect1 id="checking">
325
310
<title>CHECKING</title>
327
312
The server will, by default, continually check that the clients
328
313
are still up. If a client has not been confirmed as being up
329
314
for some time, the client is assumed to be compromised and is no
330
longer eligible to receive the encrypted password. (Manual
331
intervention is required to re-enable a client.) The timeout,
315
longer eligible to receive the encrypted password. The timeout,
332
316
checker program, and interval between checks can be configured
333
317
both globally and per client; see <citerefentry>
334
318
<refentrytitle>mandos-clients.conf</refentrytitle>
335
<manvolnum>5</manvolnum></citerefentry>. A client successfully
336
receiving its password will also be treated as a successful
341
<refsect1 id="approval">
342
<title>APPROVAL</title>
344
The server can be configured to require manual approval for a
345
client before it is sent its secret. The delay to wait for such
346
approval and the default action (approve or deny) can be
347
configured both globally and per client; see <citerefentry>
348
<refentrytitle>mandos-clients.conf</refentrytitle>
349
<manvolnum>5</manvolnum></citerefentry>. By default all clients
350
will be approved immediately without delay.
353
This can be used to deny a client its secret if not manually
354
approved within a specified time. It can also be used to make
355
the server delay before giving a client its secret, allowing
356
optional manual denying of this specific client.
319
<manvolnum>5</manvolnum></citerefentry>.
361
323
<refsect1 id="logging">
362
324
<title>LOGGING</title>
367
329
and also show them on the console.
371
<refsect1 id="dbus_interface">
372
<title>D-BUS INTERFACE</title>
374
The server will by default provide a D-Bus system bus interface.
375
This interface will only be accessible by the root user or a
376
Mandos-specific user, if such a user exists. For documentation
377
of the D-Bus API, see the file <filename>DBUS-API</filename>.
381
333
<refsect1 id="exit_status">
382
334
<title>EXIT STATUS</title>
438
<term><filename>/var/run/mandos.pid</filename></term>
390
<term><filename>/var/run/mandos/mandos.pid</filename></term>
441
The file containing the process id of the
442
<command>&COMMANDNAME;</command> process started last.
393
The file containing the process id of
394
<command>&COMMANDNAME;</command>.
473
425
backtrace. This could be considered a feature.
476
Currently, if a client is disabled due to having timed out, the
477
server does not record this fact onto permanent storage. This
478
has some security implications, see <xref linkend="clients"/>.
428
Currently, if a client is declared <quote>invalid</quote> due to
429
having timed out, the server does not record this fact onto
430
permanent storage. This has some security implications, see
431
<xref linkend="CLIENTS"/>.
434
There is currently no way of querying the server of the current
435
status of clients, other than analyzing its <systemitem
436
class="service">syslog</systemitem> output.
481
439
There is no fine-grained control over logging and debug output.
530
484
</informalexample>
533
487
<refsect1 id="security">
534
488
<title>SECURITY</title>
535
<refsect2 id="server">
489
<refsect2 id="SERVER">
536
490
<title>SERVER</title>
538
492
Running this <command>&COMMANDNAME;</command> server program
539
493
should not in itself present any security risk to the host
540
computer running it. The program switches to a non-root user
494
computer running it. The program does not need any special
495
privileges to run, and is designed to run as a non-root user.
544
<refsect2 id="clients">
498
<refsect2 id="CLIENTS">
545
499
<title>CLIENTS</title>
547
501
The server only gives out its stored data to clients which
554
508
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
555
509
<manvolnum>5</manvolnum></citerefentry>)
556
510
<emphasis>must</emphasis> be made non-readable by anyone
557
except the user starting the server (usually root).
511
except the user running the server.
560
514
As detailed in <xref linkend="checking"/>, the status of all
565
519
If a client is compromised, its downtime should be duly noted
566
by the server which would therefore disable the client. But
567
if the server was ever restarted, it would re-read its client
568
list from its configuration file and again regard all clients
569
therein as enabled, and hence eligible to receive their
570
passwords. Therefore, be careful when restarting servers if
571
it is suspected that a client has, in fact, been compromised
572
by parties who may now be running a fake Mandos client with
573
the keys from the non-encrypted initial <acronym>RAM</acronym>
574
image of the client host. What should be done in that case
575
(if restarting the server program really is necessary) is to
576
stop the server program, edit the configuration file to omit
577
any suspect clients, and restart the server program.
520
by the server which would therefore declare the client
521
invalid. But if the server was ever restarted, it would
522
re-read its client list from its configuration file and again
523
regard all clients therein as valid, and hence eligible to
524
receive their passwords. Therefore, be careful when
525
restarting servers if it is suspected that a client has, in
526
fact, been compromised by parties who may now be running a
527
fake Mandos client with the keys from the non-encrypted
528
initial RAM image of the client host. What should be done in
529
that case (if restarting the server program really is
530
necessary) is to stop the server program, edit the
531
configuration file to omit any suspect clients, and restart
580
535
For more details on client-side security, see
581
<citerefentry><refentrytitle>mandos-client</refentrytitle>
536
<citerefentry><refentrytitle>password-request</refentrytitle>
582
537
<manvolnum>8mandos</manvolnum></citerefentry>.
587
542
<refsect1 id="see_also">
588
543
<title>SEE ALSO</title>
592
547
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
593
548
<refentrytitle>mandos.conf</refentrytitle>
594
549
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
595
<refentrytitle>mandos-client</refentrytitle>
550
<refentrytitle>password-request</refentrytitle>
596
551
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
597
552
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>