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-25">
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
36
<holder>Teddy Hogeborn</holder>
35
37
<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/"/>.
39
<xi:include href="legalnotice.xml"/>
63
43
<refentrytitle>&COMMANDNAME;</refentrytitle>
64
44
<manvolnum>8</manvolnum>
105
85
<replaceable>DIRECTORY</replaceable></option></arg>
107
87
<arg><option>--debug</option></arg>
89
<arg><option>--no-dbus</option></arg>
91
<arg><option>--no-ipv6</option></arg>
110
94
<command>&COMMANDNAME;</command>
137
121
Any authenticated client is then given the stored pre-encrypted
138
122
password for that specific client.
143
126
<refsect1 id="purpose">
144
127
<title>PURPOSE</title>
147
129
The purpose of this is to enable <emphasis>remote and unattended
148
130
rebooting</emphasis> of client host computer with an
149
131
<emphasis>encrypted root file system</emphasis>. See <xref
150
132
linkend="overview"/> for details.
155
136
<refsect1 id="options">
156
137
<title>OPTIONS</title>
160
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"/>
259
256
<refsect1 id="overview">
260
257
<title>OVERVIEW</title>
261
258
<xi:include href="overview.xml"/>
263
260
This program is the server part. It is a normal server program
264
261
and will run in a normal system environment, not in an initial
265
RAM disk environment.
262
<acronym>RAM</acronym> disk environment.
269
266
<refsect1 id="protocol">
270
267
<title>NETWORK PROTOCOL</title>
324
321
</tbody></tgroup></table>
327
324
<refsect1 id="checking">
328
325
<title>CHECKING</title>
330
327
The server will, by default, continually check that the clients
331
328
are still up. If a client has not been confirmed as being up
332
329
for some time, the client is assumed to be compromised and is no
333
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,
334
332
checker program, and interval between checks can be configured
335
333
both globally and per client; see <citerefentry>
336
334
<refentrytitle>mandos-clients.conf</refentrytitle>
337
<manvolnum>5</manvolnum></citerefentry>.
335
<manvolnum>5</manvolnum></citerefentry>. A client successfully
336
receiving its password will also be treated as a successful
341
341
<refsect1 id="logging">
342
342
<title>LOGGING</title>
347
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>.
351
361
<refsect1 id="exit_status">
352
362
<title>EXIT STATUS</title>
408
<term><filename>/var/run/mandos/mandos.pid</filename></term>
418
<term><filename>/var/run/mandos.pid</filename></term>
411
The file containing the process id of
412
<command>&COMMANDNAME;</command>.
421
The file containing the process id of the
422
<command>&COMMANDNAME;</command> process started last.
443
453
backtrace. This could be considered a feature.
446
Currently, if a client is declared <quote>invalid</quote> due to
447
having timed out, the server does not record this fact onto
448
permanent storage. This has some security implications, see
449
<xref linkend="CLIENTS"/>.
452
There is currently no way of querying the server of the current
453
status of clients, other than analyzing its <systemitem
454
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"/>.
457
461
There is no fine-grained control over logging and debug output.
460
464
Debug mode is conflated with running in the foreground.
463
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
502
510
</informalexample>
505
513
<refsect1 id="security">
506
514
<title>SECURITY</title>
507
<refsect2 id="SERVER">
515
<refsect2 id="server">
508
516
<title>SERVER</title>
510
518
Running this <command>&COMMANDNAME;</command> server program
511
519
should not in itself present any security risk to the host
512
computer running it. The program does not need any special
513
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
516
<refsect2 id="CLIENTS">
524
<refsect2 id="clients">
517
525
<title>CLIENTS</title>
519
527
The server only gives out its stored data to clients which
526
534
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
527
535
<manvolnum>5</manvolnum></citerefentry>)
528
536
<emphasis>must</emphasis> be made non-readable by anyone
529
except the user running the server.
537
except the user starting the server (usually root).
532
540
As detailed in <xref linkend="checking"/>, the status of all
537
545
If a client is compromised, its downtime should be duly noted
538
by the server which would therefore declare the client
539
invalid. But if the server was ever restarted, it would
540
re-read its client list from its configuration file and again
541
regard all clients therein as valid, and hence eligible to
542
receive their passwords. Therefore, be careful when
543
restarting servers if it is suspected that a client has, in
544
fact, been compromised by parties who may now be running a
545
fake Mandos client with the keys from the non-encrypted
546
initial RAM image of the client host. What should be done in
547
that case (if restarting the server program really is
548
necessary) is to stop the server program, edit the
549
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.
553
560
For more details on client-side security, see
554
<citerefentry><refentrytitle>password-request</refentrytitle>
561
<citerefentry><refentrytitle>mandos-client</refentrytitle>
555
562
<manvolnum>8mandos</manvolnum></citerefentry>.
560
567
<refsect1 id="see_also">
561
568
<title>SEE ALSO</title>
565
572
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
566
573
<refentrytitle>mandos.conf</refentrytitle>
567
574
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
568
<refentrytitle>password-request</refentrytitle>
575
<refentrytitle>mandos-client</refentrytitle>
569
576
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
570
577
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>