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-26">
6
<!ENTITY % common SYSTEM "common.ent">
6
<!ENTITY TIMESTAMP "2008-08-29">
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>
37
34
<holder>Teddy Hogeborn</holder>
38
35
<holder>Björn Påhlsson</holder>
40
<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/"/>.
44
63
<refentrytitle>&COMMANDNAME;</refentrytitle>
45
64
<manvolnum>8</manvolnum>
49
68
<refname><command>&COMMANDNAME;</command></refname>
51
Gives encrypted passwords to authenticated Mandos clients
70
Sends encrypted passwords to authenticated Mandos clients
57
76
<command>&COMMANDNAME;</command>
59
<arg choice="plain"><option>--interface
60
<replaceable>NAME</replaceable></option></arg>
61
<arg choice="plain"><option>-i
62
<replaceable>NAME</replaceable></option></arg>
66
<arg choice="plain"><option>--address
67
<replaceable>ADDRESS</replaceable></option></arg>
68
<arg choice="plain"><option>-a
69
<replaceable>ADDRESS</replaceable></option></arg>
73
<arg choice="plain"><option>--port
74
<replaceable>PORT</replaceable></option></arg>
75
<arg choice="plain"><option>-p
76
<replaceable>PORT</replaceable></option></arg>
79
<arg><option>--priority
80
<replaceable>PRIORITY</replaceable></option></arg>
82
<arg><option>--servicename
83
<replaceable>NAME</replaceable></option></arg>
85
<arg><option>--configdir
86
<replaceable>DIRECTORY</replaceable></option></arg>
88
<arg><option>--debug</option></arg>
90
<arg><option>--no-dbus</option></arg>
92
<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>
95
96
<command>&COMMANDNAME;</command>
96
97
<group choice="req">
97
<arg choice="plain"><option>--help</option></arg>
98
<arg choice="plain"><option>-h</option></arg>
98
<arg choice="plain">-h</arg>
99
<arg choice="plain">--help</arg>
102
103
<command>&COMMANDNAME;</command>
103
<arg choice="plain"><option>--version</option></arg>
104
<arg choice="plain">--version</arg>
106
107
<command>&COMMANDNAME;</command>
107
<arg choice="plain"><option>--check</option></arg>
108
<arg choice="plain">--check</arg>
109
110
</refsynopsisdiv>
111
112
<refsect1 id="description">
112
113
<title>DESCRIPTION</title>
122
123
Any authenticated client is then given the stored pre-encrypted
123
124
password for that specific client.
127
129
<refsect1 id="purpose">
128
130
<title>PURPOSE</title>
130
133
The purpose of this is to enable <emphasis>remote and unattended
131
134
rebooting</emphasis> of client host computer with an
132
135
<emphasis>encrypted root file system</emphasis>. See <xref
133
136
linkend="overview"/> for details.
137
141
<refsect1 id="options">
138
142
<title>OPTIONS</title>
141
<term><option>--help</option></term>
142
<term><option>-h</option></term>
146
<term><literal>-h</literal>, <literal>--help</literal></term>
145
149
Show a help message and exit
151
<term><option>--interface</option>
152
<replaceable>NAME</replaceable></term>
153
<term><option>-i</option>
154
<replaceable>NAME</replaceable></term>
155
<term><literal>-i</literal>, <literal>--interface <replaceable
156
>NAME</replaceable></literal></term>
156
158
<xi:include href="mandos-options.xml" xpointer="interface"/>
161
<term><option>--address
162
<replaceable>ADDRESS</replaceable></option></term>
164
<replaceable>ADDRESS</replaceable></option></term>
163
<term><literal>-a</literal>, <literal>--address <replaceable>
164
ADDRESS</replaceable></literal></term>
166
166
<xi:include href="mandos-options.xml" xpointer="address"/>
172
<replaceable>PORT</replaceable></option></term>
174
<replaceable>PORT</replaceable></option></term>
171
<term><literal>-p</literal>, <literal>--port <replaceable>
172
PORT</replaceable></literal></term>
176
174
<xi:include href="mandos-options.xml" xpointer="port"/>
181
<term><option>--check</option></term>
179
<term><literal>--check</literal></term>
184
182
Run the server’s self-tests. This includes any unit
191
<term><option>--debug</option></term>
189
<term><literal>--debug</literal></term>
193
191
<xi:include href="mandos-options.xml" xpointer="debug"/>
198
<term><option>--priority <replaceable>
199
PRIORITY</replaceable></option></term>
196
<term><literal>--priority <replaceable>
197
PRIORITY</replaceable></literal></term>
201
199
<xi:include href="mandos-options.xml" xpointer="priority"/>
206
<term><option>--servicename
207
<replaceable>NAME</replaceable></option></term>
204
<term><literal>--servicename <replaceable>NAME</replaceable>
209
207
<xi:include href="mandos-options.xml"
210
208
xpointer="servicename"/>
215
<term><option>--configdir
216
<replaceable>DIRECTORY</replaceable></option></term>
213
<term><literal>--configdir <replaceable>DIR</replaceable>
219
217
Directory to search for configuration files. Default is
230
<term><option>--version</option></term>
228
<term><literal>--version</literal></term>
233
231
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"/>
257
238
<refsect1 id="overview">
258
239
<title>OVERVIEW</title>
259
240
<xi:include href="overview.xml"/>
261
242
This program is the server part. It is a normal server program
262
243
and will run in a normal system environment, not in an initial
263
<acronym>RAM</acronym> disk environment.
244
RAM disk environment.
267
248
<refsect1 id="protocol">
268
249
<title>NETWORK PROTOCOL</title>
322
303
</tbody></tgroup></table>
325
306
<refsect1 id="checking">
326
307
<title>CHECKING</title>
328
309
The server will, by default, continually check that the clients
329
310
are still up. If a client has not been confirmed as being up
330
311
for some time, the client is assumed to be compromised and is no
331
longer eligible to receive the encrypted password. (Manual
332
intervention is required to re-enable a client.) The timeout,
312
longer eligible to receive the encrypted password. The timeout,
333
313
checker program, and interval between checks can be configured
334
314
both globally and per client; see <citerefentry>
335
315
<refentrytitle>mandos-clients.conf</refentrytitle>
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.
316
<manvolnum>5</manvolnum></citerefentry>.
362
320
<refsect1 id="logging">
363
321
<title>LOGGING</title>
368
326
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>.
382
330
<refsect1 id="exit_status">
383
331
<title>EXIT STATUS</title>
474
422
backtrace. This could be considered a feature.
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"/>.
425
Currently, if a client is declared <quote>invalid</quote> due to
426
having timed out, the server does not record this fact onto
427
permanent storage. This has some security implications, see
428
<xref linkend="CLIENTS"/>.
431
There is currently no way of querying the server of the current
432
status of clients, other than analyzing its <systemitem
433
class="service">syslog</systemitem> output.
482
436
There is no fine-grained control over logging and debug output.
531
481
</informalexample>
534
484
<refsect1 id="security">
535
485
<title>SECURITY</title>
536
<refsect2 id="server">
486
<refsect2 id="SERVER">
537
487
<title>SERVER</title>
539
489
Running this <command>&COMMANDNAME;</command> server program
540
490
should not in itself present any security risk to the host
541
computer running it. The program switches to a non-root user
491
computer running it. The program does not need any special
492
privileges to run, and is designed to run as a non-root user.
545
<refsect2 id="clients">
495
<refsect2 id="CLIENTS">
546
496
<title>CLIENTS</title>
548
498
The server only gives out its stored data to clients which
555
505
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
556
506
<manvolnum>5</manvolnum></citerefentry>)
557
507
<emphasis>must</emphasis> be made non-readable by anyone
558
except the user starting the server (usually root).
508
except the user running the server.
561
511
As detailed in <xref linkend="checking"/>, the status of all
566
516
If a client is compromised, its downtime should be duly noted
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.
517
by the server which would therefore declare the client
518
invalid. But if the server was ever restarted, it would
519
re-read its client list from its configuration file and again
520
regard all clients therein as valid, and hence eligible to
521
receive their passwords. Therefore, be careful when
522
restarting servers if it is suspected that a client has, in
523
fact, been compromised by parties who may now be running a
524
fake Mandos client with the keys from the non-encrypted
525
initial RAM image of the client host. What should be done in
526
that case (if restarting the server program really is
527
necessary) is to stop the server program, edit the
528
configuration file to omit any suspect clients, and restart
581
532
For more details on client-side security, see
582
<citerefentry><refentrytitle>mandos-client</refentrytitle>
533
<citerefentry><refentrytitle>password-request</refentrytitle>
583
534
<manvolnum>8mandos</manvolnum></citerefentry>.
588
539
<refsect1 id="see_also">
589
540
<title>SEE ALSO</title>
593
544
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
594
545
<refentrytitle>mandos.conf</refentrytitle>
595
546
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
596
<refentrytitle>mandos-client</refentrytitle>
547
<refentrytitle>password-request</refentrytitle>
597
548
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
598
549
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>