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 "2010-09-26">
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>
34
37
<holder>Teddy Hogeborn</holder>
35
38
<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/"/>.
40
<xi:include href="legalnotice.xml"/>
63
44
<refentrytitle>&COMMANDNAME;</refentrytitle>
64
45
<manvolnum>8</manvolnum>
105
86
<replaceable>DIRECTORY</replaceable></option></arg>
107
88
<arg><option>--debug</option></arg>
90
<arg><option>--no-dbus</option></arg>
92
<arg><option>--no-ipv6</option></arg>
110
95
<command>&COMMANDNAME;</command>
137
122
Any authenticated client is then given the stored pre-encrypted
138
123
password for that specific client.
143
127
<refsect1 id="purpose">
144
128
<title>PURPOSE</title>
147
130
The purpose of this is to enable <emphasis>remote and unattended
148
131
rebooting</emphasis> of client host computer with an
149
132
<emphasis>encrypted root file system</emphasis>. See <xref
150
133
linkend="overview"/> for details.
155
137
<refsect1 id="options">
156
138
<title>OPTIONS</title>
141
<term><option>--help</option></term>
160
142
<term><option>-h</option></term>
161
<term><option>--help</option></term>
164
145
Show a help message and exit
151
<term><option>--interface</option>
152
<replaceable>NAME</replaceable></term>
170
153
<term><option>-i</option>
171
154
<replaceable>NAME</replaceable></term>
172
<term><option>--interface</option>
173
<replaceable>NAME</replaceable></term>
175
156
<xi:include href="mandos-options.xml" xpointer="interface"/>
180
<term><literal>-a</literal>, <literal>--address <replaceable>
181
ADDRESS</replaceable></literal></term>
161
<term><option>--address
162
<replaceable>ADDRESS</replaceable></option></term>
164
<replaceable>ADDRESS</replaceable></option></term>
183
166
<xi:include href="mandos-options.xml" xpointer="address"/>
188
<term><literal>-p</literal>, <literal>--port <replaceable>
189
PORT</replaceable></literal></term>
172
<replaceable>PORT</replaceable></option></term>
174
<replaceable>PORT</replaceable></option></term>
191
176
<xi:include href="mandos-options.xml" xpointer="port"/>
196
<term><literal>--check</literal></term>
181
<term><option>--check</option></term>
199
184
Run the server’s self-tests. This includes any unit
206
<term><literal>--debug</literal></term>
191
<term><option>--debug</option></term>
208
193
<xi:include href="mandos-options.xml" xpointer="debug"/>
213
<term><literal>--priority <replaceable>
214
PRIORITY</replaceable></literal></term>
198
<term><option>--priority <replaceable>
199
PRIORITY</replaceable></option></term>
216
201
<xi:include href="mandos-options.xml" xpointer="priority"/>
221
<term><literal>--servicename <replaceable>NAME</replaceable>
206
<term><option>--servicename
207
<replaceable>NAME</replaceable></option></term>
224
209
<xi:include href="mandos-options.xml"
225
210
xpointer="servicename"/>
230
<term><literal>--configdir <replaceable>DIR</replaceable>
215
<term><option>--configdir
216
<replaceable>DIRECTORY</replaceable></option></term>
234
219
Directory to search for configuration files. Default is
245
<term><literal>--version</literal></term>
230
<term><option>--version</option></term>
248
233
Prints the program version and exit.
239
<term><option>--no-dbus</option></term>
241
<xi:include href="mandos-options.xml" xpointer="dbus"/>
243
See also <xref linkend="dbus_interface"/>.
249
<term><option>--no-ipv6</option></term>
251
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
255
257
<refsect1 id="overview">
256
258
<title>OVERVIEW</title>
257
259
<xi:include href="overview.xml"/>
259
261
This program is the server part. It is a normal server program
260
262
and will run in a normal system environment, not in an initial
261
RAM disk environment.
263
<acronym>RAM</acronym> disk environment.
265
267
<refsect1 id="protocol">
266
268
<title>NETWORK PROTOCOL</title>
320
322
</tbody></tgroup></table>
323
325
<refsect1 id="checking">
324
326
<title>CHECKING</title>
326
328
The server will, by default, continually check that the clients
327
329
are still up. If a client has not been confirmed as being up
328
330
for some time, the client is assumed to be compromised and is no
329
longer eligible to receive the encrypted password. The timeout,
331
longer eligible to receive the encrypted password. (Manual
332
intervention is required to re-enable a client.) The timeout,
330
333
checker program, and interval between checks can be configured
331
334
both globally and per client; see <citerefentry>
332
335
<refentrytitle>mandos-clients.conf</refentrytitle>
333
<manvolnum>5</manvolnum></citerefentry>.
336
<manvolnum>5</manvolnum></citerefentry>. A client successfully
337
receiving its password will also be treated as a successful
342
<refsect1 id="approval">
343
<title>APPROVAL</title>
345
The server can be configured to require manual approval for a
346
client before it is sent its secret. The delay to wait for such
347
approval and the default action (approve or deny) can be
348
configured both globally and per client; see <citerefentry>
349
<refentrytitle>mandos-clients.conf</refentrytitle>
350
<manvolnum>5</manvolnum></citerefentry>. By default all clients
351
will be approved immediately without delay.
354
This can be used to deny a client its secret if not manually
355
approved within a specified time. It can also be used to make
356
the server delay before giving a client its secret, allowing
357
optional manual denying of this specific client.
337
362
<refsect1 id="logging">
338
363
<title>LOGGING</title>
343
368
and also show them on the console.
372
<refsect1 id="dbus_interface">
373
<title>D-BUS INTERFACE</title>
375
The server will by default provide a D-Bus system bus interface.
376
This interface will only be accessible by the root user or a
377
Mandos-specific user, if such a user exists. For documentation
378
of the D-Bus API, see the file <filename>DBUS-API</filename>.
347
382
<refsect1 id="exit_status">
348
383
<title>EXIT STATUS</title>
404
<term><filename>/var/run/mandos/mandos.pid</filename></term>
439
<term><filename>/var/run/mandos.pid</filename></term>
407
The file containing the process id of
408
<command>&COMMANDNAME;</command>.
442
The file containing the process id of the
443
<command>&COMMANDNAME;</command> process started last.
439
474
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.
477
Currently, if a client is disabled due to having timed out, the
478
server does not record this fact onto permanent storage. This
479
has some security implications, see <xref linkend="clients"/>.
453
482
There is no fine-grained control over logging and debug output.
456
485
Debug mode is conflated with running in the foreground.
459
The console log messages does not show a timestamp.
488
The console log messages do not show a time stamp.
491
This server does not check the expire time of clients’ OpenPGP
498
531
</informalexample>
501
534
<refsect1 id="security">
502
535
<title>SECURITY</title>
503
<refsect2 id="SERVER">
536
<refsect2 id="server">
504
537
<title>SERVER</title>
506
539
Running this <command>&COMMANDNAME;</command> server program
507
540
should not in itself present any security risk to the host
508
computer running it. The program does not need any special
509
privileges to run, and is designed to run as a non-root user.
541
computer running it. The program switches to a non-root user
512
<refsect2 id="CLIENTS">
545
<refsect2 id="clients">
513
546
<title>CLIENTS</title>
515
548
The server only gives out its stored data to clients which
522
555
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
523
556
<manvolnum>5</manvolnum></citerefentry>)
524
557
<emphasis>must</emphasis> be made non-readable by anyone
525
except the user running the server.
558
except the user starting the server (usually root).
528
561
As detailed in <xref linkend="checking"/>, the status of all
533
566
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
567
by the server which would therefore disable the client. But
568
if the server was ever restarted, it would re-read its client
569
list from its configuration file and again regard all clients
570
therein as enabled, and hence eligible to receive their
571
passwords. Therefore, be careful when restarting servers if
572
it is suspected that a client has, in fact, been compromised
573
by parties who may now be running a fake Mandos client with
574
the keys from the non-encrypted initial <acronym>RAM</acronym>
575
image of the client host. What should be done in that case
576
(if restarting the server program really is necessary) is to
577
stop the server program, edit the configuration file to omit
578
any suspect clients, and restart the server program.
549
581
For more details on client-side security, see
550
<citerefentry><refentrytitle>password-request</refentrytitle>
582
<citerefentry><refentrytitle>mandos-client</refentrytitle>
551
583
<manvolnum>8mandos</manvolnum></citerefentry>.
556
588
<refsect1 id="see_also">
557
589
<title>SEE ALSO</title>
561
593
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
562
594
<refentrytitle>mandos.conf</refentrytitle>
563
595
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
564
<refentrytitle>password-request</refentrytitle>
596
<refentrytitle>mandos-client</refentrytitle>
565
597
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
566
598
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>