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-31">
5
<!ENTITY TIMESTAMP "2010-09-11">
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>
83
85
<replaceable>DIRECTORY</replaceable></option></arg>
85
87
<arg><option>--debug</option></arg>
89
<arg><option>--no-dbus</option></arg>
91
<arg><option>--no-ipv6</option></arg>
88
94
<command>&COMMANDNAME;</command>
115
121
Any authenticated client is then given the stored pre-encrypted
116
122
password for that specific client.
121
126
<refsect1 id="purpose">
122
127
<title>PURPOSE</title>
125
129
The purpose of this is to enable <emphasis>remote and unattended
126
130
rebooting</emphasis> of client host computer with an
127
131
<emphasis>encrypted root file system</emphasis>. See <xref
128
132
linkend="overview"/> for details.
133
136
<refsect1 id="options">
134
137
<title>OPTIONS</title>
138
140
<term><option>--help</option></term>
238
<term><option>--no-dbus</option></term>
240
<xi:include href="mandos-options.xml" xpointer="dbus"/>
242
See also <xref linkend="dbus_interface"/>.
248
<term><option>--no-ipv6</option></term>
250
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
237
256
<refsect1 id="overview">
238
257
<title>OVERVIEW</title>
239
258
<xi:include href="overview.xml"/>
241
260
This program is the server part. It is a normal server program
242
261
and will run in a normal system environment, not in an initial
243
RAM disk environment.
262
<acronym>RAM</acronym> disk environment.
247
266
<refsect1 id="protocol">
248
267
<title>NETWORK PROTOCOL</title>
302
321
</tbody></tgroup></table>
305
324
<refsect1 id="checking">
306
325
<title>CHECKING</title>
308
327
The server will, by default, continually check that the clients
309
328
are still up. If a client has not been confirmed as being up
310
329
for some time, the client is assumed to be compromised and is no
311
longer eligible to receive the encrypted password. The timeout,
330
longer eligible to receive the encrypted password. (Manual
331
intervention is required to re-enable a client.) The timeout,
312
332
checker program, and interval between checks can be configured
313
333
both globally and per client; see <citerefentry>
314
334
<refentrytitle>mandos-clients.conf</refentrytitle>
315
<manvolnum>5</manvolnum></citerefentry>.
335
<manvolnum>5</manvolnum></citerefentry>. A client successfully
336
receiving its password will also be treated as a successful
319
341
<refsect1 id="logging">
320
342
<title>LOGGING</title>
325
347
and also show them on the console.
351
<refsect1 id="dbus_interface">
352
<title>D-BUS INTERFACE</title>
354
The server will by default provide a D-Bus system bus interface.
355
This interface will only be accessible by the root user or a
356
Mandos-specific user, if such a user exists. For documentation
357
of the D-Bus API, see the file <filename>DBUS-API</filename>.
329
361
<refsect1 id="exit_status">
330
362
<title>EXIT STATUS</title>
421
453
backtrace. This could be considered a feature.
424
Currently, if a client is declared <quote>invalid</quote> due to
425
having timed out, the server does not record this fact onto
426
permanent storage. This has some security implications, see
427
<xref linkend="CLIENTS"/>.
430
There is currently no way of querying the server of the current
431
status of clients, other than analyzing its <systemitem
432
class="service">syslog</systemitem> output.
456
Currently, if a client is disabled due to having timed out, the
457
server does not record this fact onto permanent storage. This
458
has some security implications, see <xref linkend="clients"/>.
435
461
There is no fine-grained control over logging and debug output.
438
464
Debug mode is conflated with running in the foreground.
441
The console log messages does not show a timestamp.
467
The console log messages do not show a time stamp.
470
This server does not check the expire time of clients’ OpenPGP
480
510
</informalexample>
483
513
<refsect1 id="security">
484
514
<title>SECURITY</title>
485
<refsect2 id="SERVER">
515
<refsect2 id="server">
486
516
<title>SERVER</title>
488
518
Running this <command>&COMMANDNAME;</command> server program
489
519
should not in itself present any security risk to the host
490
computer running it. The program does not need any special
491
privileges to run, and is designed to run as a non-root user.
520
computer running it. The program switches to a non-root user
494
<refsect2 id="CLIENTS">
524
<refsect2 id="clients">
495
525
<title>CLIENTS</title>
497
527
The server only gives out its stored data to clients which
504
534
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
505
535
<manvolnum>5</manvolnum></citerefentry>)
506
536
<emphasis>must</emphasis> be made non-readable by anyone
507
except the user running the server.
537
except the user starting the server (usually root).
510
540
As detailed in <xref linkend="checking"/>, the status of all
515
545
If a client is compromised, its downtime should be duly noted
516
by the server which would therefore declare the client
517
invalid. But if the server was ever restarted, it would
518
re-read its client list from its configuration file and again
519
regard all clients therein as valid, and hence eligible to
520
receive their passwords. Therefore, be careful when
521
restarting servers if it is suspected that a client has, in
522
fact, been compromised by parties who may now be running a
523
fake Mandos client with the keys from the non-encrypted
524
initial RAM image of the client host. What should be done in
525
that case (if restarting the server program really is
526
necessary) is to stop the server program, edit the
527
configuration file to omit any suspect clients, and restart
546
by the server which would therefore disable the client. But
547
if the server was ever restarted, it would re-read its client
548
list from its configuration file and again regard all clients
549
therein as enabled, and hence eligible to receive their
550
passwords. Therefore, be careful when restarting servers if
551
it is suspected that a client has, in fact, been compromised
552
by parties who may now be running a fake Mandos client with
553
the keys from the non-encrypted initial <acronym>RAM</acronym>
554
image of the client host. What should be done in that case
555
(if restarting the server program really is necessary) is to
556
stop the server program, edit the configuration file to omit
557
any suspect clients, and restart the server program.
531
560
For more details on client-side security, see
532
<citerefentry><refentrytitle>password-request</refentrytitle>
561
<citerefentry><refentrytitle>mandos-client</refentrytitle>
533
562
<manvolnum>8mandos</manvolnum></citerefentry>.
538
567
<refsect1 id="see_also">
539
568
<title>SEE ALSO</title>
543
572
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
544
573
<refentrytitle>mandos.conf</refentrytitle>
545
574
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
546
<refentrytitle>password-request</refentrytitle>
575
<refentrytitle>mandos-client</refentrytitle>
547
576
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
548
577
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
added
removed
mandos.xml
