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 "2011-02-27">
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>
38
34
<holder>Teddy Hogeborn</holder>
39
35
<holder>Björn Påhlsson</holder>
41
<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/"/>.
45
63
<refentrytitle>&COMMANDNAME;</refentrytitle>
46
64
<manvolnum>8</manvolnum>
52
70
Gives encrypted passwords to authenticated Mandos clients
58
76
<command>&COMMANDNAME;</command>
60
<arg choice="plain"><option>--interface
61
<replaceable>NAME</replaceable></option></arg>
62
<arg choice="plain"><option>-i
63
<replaceable>NAME</replaceable></option></arg>
67
<arg choice="plain"><option>--address
68
<replaceable>ADDRESS</replaceable></option></arg>
69
<arg choice="plain"><option>-a
70
<replaceable>ADDRESS</replaceable></option></arg>
74
<arg choice="plain"><option>--port
75
<replaceable>PORT</replaceable></option></arg>
76
<arg choice="plain"><option>-p
77
<replaceable>PORT</replaceable></option></arg>
80
<arg><option>--priority
81
<replaceable>PRIORITY</replaceable></option></arg>
83
<arg><option>--servicename
84
<replaceable>NAME</replaceable></option></arg>
86
<arg><option>--configdir
87
<replaceable>DIRECTORY</replaceable></option></arg>
89
<arg><option>--debug</option></arg>
91
<arg><option>--debuglevel
92
<replaceable>LEVEL</replaceable></option></arg>
94
<arg><option>--no-dbus</option></arg>
96
<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>
99
96
<command>&COMMANDNAME;</command>
100
97
<group choice="req">
101
<arg choice="plain"><option>--help</option></arg>
102
<arg choice="plain"><option>-h</option></arg>
98
<arg choice="plain">-h</arg>
99
<arg choice="plain">--help</arg>
106
103
<command>&COMMANDNAME;</command>
107
<arg choice="plain"><option>--version</option></arg>
104
<arg choice="plain">--version</arg>
110
107
<command>&COMMANDNAME;</command>
111
<arg choice="plain"><option>--check</option></arg>
108
<arg choice="plain">--check</arg>
113
110
</refsynopsisdiv>
115
112
<refsect1 id="description">
116
113
<title>DESCRIPTION</title>
126
123
Any authenticated client is then given the stored pre-encrypted
127
124
password for that specific client.
131
129
<refsect1 id="purpose">
132
130
<title>PURPOSE</title>
134
133
The purpose of this is to enable <emphasis>remote and unattended
135
134
rebooting</emphasis> of client host computer with an
136
135
<emphasis>encrypted root file system</emphasis>. See <xref
137
136
linkend="overview"/> for details.
141
141
<refsect1 id="options">
142
142
<title>OPTIONS</title>
146
<term><option>-h</option></term>
145
147
<term><option>--help</option></term>
146
<term><option>-h</option></term>
149
150
Show a help message and exit
156
<term><option>-i</option>
157
<replaceable>NAME</replaceable></term>
155
158
<term><option>--interface</option>
156
159
<replaceable>NAME</replaceable></term>
157
<term><option>-i</option>
158
<replaceable>NAME</replaceable></term>
160
161
<xi:include href="mandos-options.xml" xpointer="interface"/>
165
<term><option>--address
166
<replaceable>ADDRESS</replaceable></option></term>
168
<replaceable>ADDRESS</replaceable></option></term>
166
<term><literal>-a</literal>, <literal>--address <replaceable>
167
ADDRESS</replaceable></literal></term>
170
169
<xi:include href="mandos-options.xml" xpointer="address"/>
176
<replaceable>PORT</replaceable></option></term>
178
<replaceable>PORT</replaceable></option></term>
174
<term><literal>-p</literal>, <literal>--port <replaceable>
175
PORT</replaceable></literal></term>
180
177
<xi:include href="mandos-options.xml" xpointer="port"/>
185
<term><option>--check</option></term>
182
<term><literal>--check</literal></term>
188
185
Run the server’s self-tests. This includes any unit
195
<term><option>--debug</option></term>
192
<term><literal>--debug</literal></term>
197
194
<xi:include href="mandos-options.xml" xpointer="debug"/>
202
<term><option>--debuglevel
203
<replaceable>LEVEL</replaceable></option></term>
206
Set the debugging log level.
207
<replaceable>LEVEL</replaceable> is a string, one of
208
<quote><literal>CRITICAL</literal></quote>,
209
<quote><literal>ERROR</literal></quote>,
210
<quote><literal>WARNING</literal></quote>,
211
<quote><literal>INFO</literal></quote>, or
212
<quote><literal>DEBUG</literal></quote>, in order of
213
increasing verbosity. The default level is
214
<quote><literal>WARNING</literal></quote>.
220
<term><option>--priority <replaceable>
221
PRIORITY</replaceable></option></term>
199
<term><literal>--priority <replaceable>
200
PRIORITY</replaceable></literal></term>
223
202
<xi:include href="mandos-options.xml" xpointer="priority"/>
228
<term><option>--servicename
229
<replaceable>NAME</replaceable></option></term>
207
<term><literal>--servicename <replaceable>NAME</replaceable>
231
210
<xi:include href="mandos-options.xml"
232
211
xpointer="servicename"/>
237
<term><option>--configdir
238
<replaceable>DIRECTORY</replaceable></option></term>
216
<term><literal>--configdir <replaceable>DIR</replaceable>
241
220
Directory to search for configuration files. Default is
252
<term><option>--version</option></term>
231
<term><literal>--version</literal></term>
255
234
Prints the program version and exit.
261
<term><option>--no-dbus</option></term>
263
<xi:include href="mandos-options.xml" xpointer="dbus"/>
265
See also <xref linkend="dbus_interface"/>.
271
<term><option>--no-ipv6</option></term>
273
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
279
241
<refsect1 id="overview">
280
242
<title>OVERVIEW</title>
281
243
<xi:include href="overview.xml"/>
283
245
This program is the server part. It is a normal server program
284
246
and will run in a normal system environment, not in an initial
285
<acronym>RAM</acronym> disk environment.
247
RAM disk environment.
289
251
<refsect1 id="protocol">
290
252
<title>NETWORK PROTOCOL</title>
344
306
</tbody></tgroup></table>
347
309
<refsect1 id="checking">
348
310
<title>CHECKING</title>
350
312
The server will, by default, continually check that the clients
351
313
are still up. If a client has not been confirmed as being up
352
314
for some time, the client is assumed to be compromised and is no
353
longer eligible to receive the encrypted password. (Manual
354
intervention is required to re-enable a client.) The timeout,
315
longer eligible to receive the encrypted password. The timeout,
355
316
checker program, and interval between checks can be configured
356
317
both globally and per client; see <citerefentry>
357
318
<refentrytitle>mandos-clients.conf</refentrytitle>
358
<manvolnum>5</manvolnum></citerefentry>. A client successfully
359
receiving its password will also be treated as a successful
364
<refsect1 id="approval">
365
<title>APPROVAL</title>
367
The server can be configured to require manual approval for a
368
client before it is sent its secret. The delay to wait for such
369
approval and the default action (approve or deny) can be
370
configured both globally and per client; see <citerefentry>
371
<refentrytitle>mandos-clients.conf</refentrytitle>
372
<manvolnum>5</manvolnum></citerefentry>. By default all clients
373
will be approved immediately without delay.
376
This can be used to deny a client its secret if not manually
377
approved within a specified time. It can also be used to make
378
the server delay before giving a client its secret, allowing
379
optional manual denying of this specific client.
319
<manvolnum>5</manvolnum></citerefentry>.
384
323
<refsect1 id="logging">
385
324
<title>LOGGING</title>
390
329
and also show them on the console.
394
<refsect1 id="dbus_interface">
395
<title>D-BUS INTERFACE</title>
397
The server will by default provide a D-Bus system bus interface.
398
This interface will only be accessible by the root user or a
399
Mandos-specific user, if such a user exists. For documentation
400
of the D-Bus API, see the file <filename>DBUS-API</filename>.
404
333
<refsect1 id="exit_status">
405
334
<title>EXIT STATUS</title>
496
425
backtrace. This could be considered a feature.
499
Currently, if a client is disabled due to having timed out, the
500
server does not record this fact onto permanent storage. This
501
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.
504
439
There is no fine-grained control over logging and debug output.
553
484
</informalexample>
556
487
<refsect1 id="security">
557
488
<title>SECURITY</title>
558
<refsect2 id="server">
489
<refsect2 id="SERVER">
559
490
<title>SERVER</title>
561
492
Running this <command>&COMMANDNAME;</command> server program
562
493
should not in itself present any security risk to the host
563
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.
567
<refsect2 id="clients">
498
<refsect2 id="CLIENTS">
568
499
<title>CLIENTS</title>
570
501
The server only gives out its stored data to clients which
577
508
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
578
509
<manvolnum>5</manvolnum></citerefentry>)
579
510
<emphasis>must</emphasis> be made non-readable by anyone
580
except the user starting the server (usually root).
511
except the user running the server.
583
514
As detailed in <xref linkend="checking"/>, the status of all
588
519
If a client is compromised, its downtime should be duly noted
589
by the server which would therefore disable the client. But
590
if the server was ever restarted, it would re-read its client
591
list from its configuration file and again regard all clients
592
therein as enabled, and hence eligible to receive their
593
passwords. Therefore, be careful when restarting servers if
594
it is suspected that a client has, in fact, been compromised
595
by parties who may now be running a fake Mandos client with
596
the keys from the non-encrypted initial <acronym>RAM</acronym>
597
image of the client host. What should be done in that case
598
(if restarting the server program really is necessary) is to
599
stop the server program, edit the configuration file to omit
600
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
603
535
For more details on client-side security, see
604
<citerefentry><refentrytitle>mandos-client</refentrytitle>
536
<citerefentry><refentrytitle>password-request</refentrytitle>
605
537
<manvolnum>8mandos</manvolnum></citerefentry>.
610
542
<refsect1 id="see_also">
611
543
<title>SEE ALSO</title>
615
547
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
616
548
<refentrytitle>mandos.conf</refentrytitle>
617
549
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
618
<refentrytitle>mandos-client</refentrytitle>
550
<refentrytitle>password-request</refentrytitle>
619
551
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
620
552
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>