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-30">
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>
70
51
Gives encrypted passwords to authenticated Mandos clients
76
57
<command>&COMMANDNAME;</command>
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>
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>
96
98
<command>&COMMANDNAME;</command>
97
99
<group choice="req">
98
<arg choice="plain">-h</arg>
99
<arg choice="plain">--help</arg>
100
<arg choice="plain"><option>--help</option></arg>
101
<arg choice="plain"><option>-h</option></arg>
103
105
<command>&COMMANDNAME;</command>
104
<arg choice="plain">--version</arg>
106
<arg choice="plain"><option>--version</option></arg>
107
109
<command>&COMMANDNAME;</command>
108
<arg choice="plain">--check</arg>
110
<arg choice="plain"><option>--check</option></arg>
110
112
</refsynopsisdiv>
112
114
<refsect1 id="description">
113
115
<title>DESCRIPTION</title>
123
125
Any authenticated client is then given the stored pre-encrypted
124
126
password for that specific client.
129
130
<refsect1 id="purpose">
130
131
<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.
141
140
<refsect1 id="options">
142
141
<title>OPTIONS</title>
144
<term><option>--help</option></term>
146
145
<term><option>-h</option></term>
147
<term><option>--help</option></term>
150
148
Show a help message and exit
154
<term><option>--interface</option>
155
<replaceable>NAME</replaceable></term>
156
156
<term><option>-i</option>
157
157
<replaceable>NAME</replaceable></term>
158
<term><option>--interface</option>
159
<replaceable>NAME</replaceable></term>
161
159
<xi:include href="mandos-options.xml" xpointer="interface"/>
166
<term><literal>-a</literal>, <literal>--address <replaceable>
167
ADDRESS</replaceable></literal></term>
164
<term><option>--address
165
<replaceable>ADDRESS</replaceable></option></term>
167
<replaceable>ADDRESS</replaceable></option></term>
169
169
<xi:include href="mandos-options.xml" xpointer="address"/>
174
<term><literal>-p</literal>, <literal>--port <replaceable>
175
PORT</replaceable></literal></term>
175
<replaceable>PORT</replaceable></option></term>
177
<replaceable>PORT</replaceable></option></term>
177
179
<xi:include href="mandos-options.xml" xpointer="port"/>
182
<term><literal>--check</literal></term>
184
<term><option>--check</option></term>
185
187
Run the server’s self-tests. This includes any unit
192
<term><literal>--debug</literal></term>
194
<term><option>--debug</option></term>
194
196
<xi:include href="mandos-options.xml" xpointer="debug"/>
199
<term><literal>--priority <replaceable>
200
PRIORITY</replaceable></literal></term>
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>
202
222
<xi:include href="mandos-options.xml" xpointer="priority"/>
207
<term><literal>--servicename <replaceable>NAME</replaceable>
227
<term><option>--servicename
228
<replaceable>NAME</replaceable></option></term>
210
230
<xi:include href="mandos-options.xml"
211
231
xpointer="servicename"/>
216
<term><literal>--configdir <replaceable>DIR</replaceable>
236
<term><option>--configdir
237
<replaceable>DIRECTORY</replaceable></option></term>
220
240
Directory to search for configuration files. Default is
231
<term><literal>--version</literal></term>
251
<term><option>--version</option></term>
234
254
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"/>
241
278
<refsect1 id="overview">
242
279
<title>OVERVIEW</title>
243
280
<xi:include href="overview.xml"/>
245
282
This program is the server part. It is a normal server program
246
283
and will run in a normal system environment, not in an initial
247
RAM disk environment.
284
<acronym>RAM</acronym> disk environment.
251
288
<refsect1 id="protocol">
252
289
<title>NETWORK PROTOCOL</title>
306
343
</tbody></tgroup></table>
309
346
<refsect1 id="checking">
310
347
<title>CHECKING</title>
312
349
The server will, by default, continually check that the clients
313
350
are still up. If a client has not been confirmed as being up
314
351
for some time, the client is assumed to be compromised and is no
315
longer eligible to receive the encrypted password. The timeout,
352
longer eligible to receive the encrypted password. (Manual
353
intervention is required to re-enable a client.) The timeout,
316
354
checker program, and interval between checks can be configured
317
355
both globally and per client; see <citerefentry>
318
356
<refentrytitle>mandos-clients.conf</refentrytitle>
319
<manvolnum>5</manvolnum></citerefentry>.
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.
323
383
<refsect1 id="logging">
324
384
<title>LOGGING</title>
329
389
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>.
333
403
<refsect1 id="exit_status">
334
404
<title>EXIT STATUS</title>
425
495
backtrace. This could be considered a feature.
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.
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"/>.
439
503
There is no fine-grained control over logging and debug output.
484
552
</informalexample>
487
555
<refsect1 id="security">
488
556
<title>SECURITY</title>
489
<refsect2 id="SERVER">
557
<refsect2 id="server">
490
558
<title>SERVER</title>
492
560
Running this <command>&COMMANDNAME;</command> server program
493
561
should not in itself present any security risk to the host
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.
562
computer running it. The program switches to a non-root user
498
<refsect2 id="CLIENTS">
566
<refsect2 id="clients">
499
567
<title>CLIENTS</title>
501
569
The server only gives out its stored data to clients which
508
576
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
509
577
<manvolnum>5</manvolnum></citerefentry>)
510
578
<emphasis>must</emphasis> be made non-readable by anyone
511
except the user running the server.
579
except the user starting the server (usually root).
514
582
As detailed in <xref linkend="checking"/>, the status of all
519
587
If a client is compromised, its downtime should be duly noted
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
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.
535
602
For more details on client-side security, see
536
<citerefentry><refentrytitle>password-request</refentrytitle>
603
<citerefentry><refentrytitle>mandos-client</refentrytitle>
537
604
<manvolnum>8mandos</manvolnum></citerefentry>.
542
609
<refsect1 id="see_also">
543
610
<title>SEE ALSO</title>
547
614
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
548
615
<refentrytitle>mandos.conf</refentrytitle>
549
616
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
550
<refentrytitle>password-request</refentrytitle>
617
<refentrytitle>mandos-client</refentrytitle>
551
618
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
552
619
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>