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-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>
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>
51
70
Gives 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>--debuglevel
91
<replaceable>LEVEL</replaceable></option></arg>
93
<arg><option>--no-dbus</option></arg>
95
<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>
98
96
<command>&COMMANDNAME;</command>
99
97
<group choice="req">
100
<arg choice="plain"><option>--help</option></arg>
101
<arg choice="plain"><option>-h</option></arg>
98
<arg choice="plain">-h</arg>
99
<arg choice="plain">--help</arg>
105
103
<command>&COMMANDNAME;</command>
106
<arg choice="plain"><option>--version</option></arg>
104
<arg choice="plain">--version</arg>
109
107
<command>&COMMANDNAME;</command>
110
<arg choice="plain"><option>--check</option></arg>
108
<arg choice="plain">--check</arg>
112
110
</refsynopsisdiv>
114
112
<refsect1 id="description">
115
113
<title>DESCRIPTION</title>
125
123
Any authenticated client is then given the stored pre-encrypted
126
124
password for that specific client.
130
129
<refsect1 id="purpose">
131
130
<title>PURPOSE</title>
133
133
The purpose of this is to enable <emphasis>remote and unattended
134
134
rebooting</emphasis> of client host computer with an
135
135
<emphasis>encrypted root file system</emphasis>. See <xref
136
136
linkend="overview"/> for details.
140
141
<refsect1 id="options">
141
142
<title>OPTIONS</title>
146
<term><option>-h</option></term>
144
147
<term><option>--help</option></term>
145
<term><option>-h</option></term>
148
150
Show a help message and exit
156
<term><option>-i</option>
157
<replaceable>NAME</replaceable></term>
154
158
<term><option>--interface</option>
155
159
<replaceable>NAME</replaceable></term>
156
<term><option>-i</option>
157
<replaceable>NAME</replaceable></term>
159
161
<xi:include href="mandos-options.xml" xpointer="interface"/>
164
<term><option>--address
165
<replaceable>ADDRESS</replaceable></option></term>
167
<replaceable>ADDRESS</replaceable></option></term>
166
<term><literal>-a</literal>, <literal>--address <replaceable>
167
ADDRESS</replaceable></literal></term>
169
169
<xi:include href="mandos-options.xml" xpointer="address"/>
175
<replaceable>PORT</replaceable></option></term>
177
<replaceable>PORT</replaceable></option></term>
174
<term><literal>-p</literal>, <literal>--port <replaceable>
175
PORT</replaceable></literal></term>
179
177
<xi:include href="mandos-options.xml" xpointer="port"/>
184
<term><option>--check</option></term>
182
<term><literal>--check</literal></term>
187
185
Run the server’s self-tests. This includes any unit
194
<term><option>--debug</option></term>
192
<term><literal>--debug</literal></term>
196
194
<xi:include href="mandos-options.xml" xpointer="debug"/>
201
<term><option>--debuglevel
202
<replaceable>LEVEL</replaceable></option></term>
205
Set the debugging log level.
206
<replaceable>LEVEL</replaceable> is a string, one of
207
<quote><literal>CRITICAL</literal></quote>,
208
<quote><literal>ERROR</literal></quote>,
209
<quote><literal>WARNING</literal></quote>,
210
<quote><literal>INFO</literal></quote>, or
211
<quote><literal>DEBUG</literal></quote>, in order of
212
increasing verbosity. The default level is
213
<quote><literal>WARNING</literal></quote>.
219
<term><option>--priority <replaceable>
220
PRIORITY</replaceable></option></term>
199
<term><literal>--priority <replaceable>
200
PRIORITY</replaceable></literal></term>
222
202
<xi:include href="mandos-options.xml" xpointer="priority"/>
227
<term><option>--servicename
228
<replaceable>NAME</replaceable></option></term>
207
<term><literal>--servicename <replaceable>NAME</replaceable>
230
210
<xi:include href="mandos-options.xml"
231
211
xpointer="servicename"/>
236
<term><option>--configdir
237
<replaceable>DIRECTORY</replaceable></option></term>
216
<term><literal>--configdir <replaceable>DIR</replaceable>
240
220
Directory to search for configuration files. Default is
251
<term><option>--version</option></term>
231
<term><literal>--version</literal></term>
254
234
Prints the program version and exit.
260
<term><option>--no-dbus</option></term>
262
<xi:include href="mandos-options.xml" xpointer="dbus"/>
264
See also <xref linkend="dbus_interface"/>.
270
<term><option>--no-ipv6</option></term>
272
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
278
241
<refsect1 id="overview">
279
242
<title>OVERVIEW</title>
280
243
<xi:include href="overview.xml"/>
282
245
This program is the server part. It is a normal server program
283
246
and will run in a normal system environment, not in an initial
284
<acronym>RAM</acronym> disk environment.
247
RAM disk environment.
288
251
<refsect1 id="protocol">
289
252
<title>NETWORK PROTOCOL</title>
343
306
</tbody></tgroup></table>
346
309
<refsect1 id="checking">
347
310
<title>CHECKING</title>
349
312
The server will, by default, continually check that the clients
350
313
are still up. If a client has not been confirmed as being up
351
314
for some time, the client is assumed to be compromised and is no
352
longer eligible to receive the encrypted password. (Manual
353
intervention is required to re-enable a client.) The timeout,
315
longer eligible to receive the encrypted password. The timeout,
354
316
checker program, and interval between checks can be configured
355
317
both globally and per client; see <citerefentry>
356
318
<refentrytitle>mandos-clients.conf</refentrytitle>
357
<manvolnum>5</manvolnum></citerefentry>. A client successfully
358
receiving its password will also be treated as a successful
363
<refsect1 id="approval">
364
<title>APPROVAL</title>
366
The server can be configured to require manual approval for a
367
client before it is sent its secret. The delay to wait for such
368
approval and the default action (approve or deny) can be
369
configured both globally and per client; see <citerefentry>
370
<refentrytitle>mandos-clients.conf</refentrytitle>
371
<manvolnum>5</manvolnum></citerefentry>. By default all clients
372
will be approved immediately without delay.
375
This can be used to deny a client its secret if not manually
376
approved within a specified time. It can also be used to make
377
the server delay before giving a client its secret, allowing
378
optional manual denying of this specific client.
319
<manvolnum>5</manvolnum></citerefentry>.
383
323
<refsect1 id="logging">
384
324
<title>LOGGING</title>
389
329
and also show them on the console.
393
<refsect1 id="dbus_interface">
394
<title>D-BUS INTERFACE</title>
396
The server will by default provide a D-Bus system bus interface.
397
This interface will only be accessible by the root user or a
398
Mandos-specific user, if such a user exists. For documentation
399
of the D-Bus API, see the file <filename>DBUS-API</filename>.
403
333
<refsect1 id="exit_status">
404
334
<title>EXIT STATUS</title>
495
425
backtrace. This could be considered a feature.
498
Currently, if a client is disabled due to having timed out, the
499
server does not record this fact onto permanent storage. This
500
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.
503
439
There is no fine-grained control over logging and debug output.
552
484
</informalexample>
555
487
<refsect1 id="security">
556
488
<title>SECURITY</title>
557
<refsect2 id="server">
489
<refsect2 id="SERVER">
558
490
<title>SERVER</title>
560
492
Running this <command>&COMMANDNAME;</command> server program
561
493
should not in itself present any security risk to the host
562
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.
566
<refsect2 id="clients">
498
<refsect2 id="CLIENTS">
567
499
<title>CLIENTS</title>
569
501
The server only gives out its stored data to clients which
576
508
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
577
509
<manvolnum>5</manvolnum></citerefentry>)
578
510
<emphasis>must</emphasis> be made non-readable by anyone
579
except the user starting the server (usually root).
511
except the user running the server.
582
514
As detailed in <xref linkend="checking"/>, the status of all
587
519
If a client is compromised, its downtime should be duly noted
588
by the server which would therefore disable the client. But
589
if the server was ever restarted, it would re-read its client
590
list from its configuration file and again regard all clients
591
therein as enabled, and hence eligible to receive their
592
passwords. Therefore, be careful when restarting servers if
593
it is suspected that a client has, in fact, been compromised
594
by parties who may now be running a fake Mandos client with
595
the keys from the non-encrypted initial <acronym>RAM</acronym>
596
image of the client host. What should be done in that case
597
(if restarting the server program really is necessary) is to
598
stop the server program, edit the configuration file to omit
599
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
602
535
For more details on client-side security, see
603
<citerefentry><refentrytitle>mandos-client</refentrytitle>
536
<citerefentry><refentrytitle>password-request</refentrytitle>
604
537
<manvolnum>8mandos</manvolnum></citerefentry>.
609
542
<refsect1 id="see_also">
610
543
<title>SEE ALSO</title>
614
547
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
615
548
<refentrytitle>mandos.conf</refentrytitle>
616
549
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
617
<refentrytitle>mandos-client</refentrytitle>
550
<refentrytitle>password-request</refentrytitle>
618
551
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
619
552
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>