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-08-08">
6
<!ENTITY % common SYSTEM "common.ent">
6
<!ENTITY TIMESTAMP "2008-08-31">
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>
126
137
Any authenticated client is then given the stored pre-encrypted
127
138
password for that specific client.
131
143
<refsect1 id="purpose">
132
144
<title>PURPOSE</title>
134
147
The purpose of this is to enable <emphasis>remote and unattended
135
148
rebooting</emphasis> of client host computer with an
136
149
<emphasis>encrypted root file system</emphasis>. See <xref
137
150
linkend="overview"/> for details.
141
155
<refsect1 id="options">
142
156
<title>OPTIONS</title>
160
<term><option>-h</option></term>
145
161
<term><option>--help</option></term>
146
<term><option>-h</option></term>
149
164
Show a help message and exit
170
<term><option>-i</option>
171
<replaceable>NAME</replaceable></term>
155
172
<term><option>--interface</option>
156
173
<replaceable>NAME</replaceable></term>
157
<term><option>-i</option>
158
<replaceable>NAME</replaceable></term>
160
175
<xi:include href="mandos-options.xml" xpointer="interface"/>
165
<term><option>--address
166
<replaceable>ADDRESS</replaceable></option></term>
168
<replaceable>ADDRESS</replaceable></option></term>
180
<term><literal>-a</literal>, <literal>--address <replaceable>
181
ADDRESS</replaceable></literal></term>
170
183
<xi:include href="mandos-options.xml" xpointer="address"/>
176
<replaceable>PORT</replaceable></option></term>
178
<replaceable>PORT</replaceable></option></term>
188
<term><literal>-p</literal>, <literal>--port <replaceable>
189
PORT</replaceable></literal></term>
180
191
<xi:include href="mandos-options.xml" xpointer="port"/>
185
<term><option>--check</option></term>
196
<term><literal>--check</literal></term>
188
199
Run the server’s self-tests. This includes any unit
195
<term><option>--debug</option></term>
206
<term><literal>--debug</literal></term>
197
208
<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>
213
<term><literal>--priority <replaceable>
214
PRIORITY</replaceable></literal></term>
223
216
<xi:include href="mandos-options.xml" xpointer="priority"/>
228
<term><option>--servicename
229
<replaceable>NAME</replaceable></option></term>
221
<term><literal>--servicename <replaceable>NAME</replaceable>
231
224
<xi:include href="mandos-options.xml"
232
225
xpointer="servicename"/>
237
<term><option>--configdir
238
<replaceable>DIRECTORY</replaceable></option></term>
230
<term><literal>--configdir <replaceable>DIR</replaceable>
241
234
Directory to search for configuration files. Default is
252
<term><option>--version</option></term>
245
<term><literal>--version</literal></term>
255
248
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
255
<refsect1 id="overview">
280
256
<title>OVERVIEW</title>
281
257
<xi:include href="overview.xml"/>
283
259
This program is the server part. It is a normal server program
284
260
and will run in a normal system environment, not in an initial
285
<acronym>RAM</acronym> disk environment.
261
RAM disk environment.
289
265
<refsect1 id="protocol">
290
266
<title>NETWORK PROTOCOL</title>
344
320
</tbody></tgroup></table>
347
323
<refsect1 id="checking">
348
324
<title>CHECKING</title>
350
326
The server will, by default, continually check that the clients
351
327
are still up. If a client has not been confirmed as being up
352
328
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,
329
longer eligible to receive the encrypted password. The timeout,
355
330
checker program, and interval between checks can be configured
356
331
both globally and per client; see <citerefentry>
357
332
<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.
333
<manvolnum>5</manvolnum></citerefentry>.
384
337
<refsect1 id="logging">
385
338
<title>LOGGING</title>
390
343
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
347
<refsect1 id="exit_status">
405
348
<title>EXIT STATUS</title>
496
439
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"/>.
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.
504
453
There is no fine-grained control over logging and debug output.
588
533
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.
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
603
549
For more details on client-side security, see
604
<citerefentry><refentrytitle>mandos-client</refentrytitle>
550
<citerefentry><refentrytitle>password-request</refentrytitle>
605
551
<manvolnum>8mandos</manvolnum></citerefentry>.
610
556
<refsect1 id="see_also">
611
557
<title>SEE ALSO</title>
613
<citerefentry><refentrytitle>intro</refentrytitle>
614
<manvolnum>8mandos</manvolnum></citerefentry>,
615
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
616
<manvolnum>5</manvolnum></citerefentry>,
617
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
618
<manvolnum>5</manvolnum></citerefentry>,
619
<citerefentry><refentrytitle>mandos-client</refentrytitle>
620
<manvolnum>8mandos</manvolnum></citerefentry>,
621
<citerefentry><refentrytitle>sh</refentrytitle>
622
<manvolnum>1</manvolnum></citerefentry>
560
<refentrytitle>mandos-clients.conf</refentrytitle>
561
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
562
<refentrytitle>mandos.conf</refentrytitle>
563
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
564
<refentrytitle>password-request</refentrytitle>
565
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
566
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>