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-09-05">
5
<!ENTITY TIMESTAMP "2009-12-09">
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>
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"/>
233
256
<refsect1 id="overview">
234
257
<title>OVERVIEW</title>
235
258
<xi:include href="overview.xml"/>
298
321
</tbody></tgroup></table>
301
324
<refsect1 id="checking">
302
325
<title>CHECKING</title>
304
327
The server will, by default, continually check that the clients
305
328
are still up. If a client has not been confirmed as being up
306
329
for some time, the client is assumed to be compromised and is no
307
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,
308
332
checker program, and interval between checks can be configured
309
333
both globally and per client; see <citerefentry>
310
334
<refentrytitle>mandos-clients.conf</refentrytitle>
311
<manvolnum>5</manvolnum></citerefentry>.
335
<manvolnum>5</manvolnum></citerefentry>. A client successfully
336
receiving its password will also be treated as a successful
315
341
<refsect1 id="logging">
316
342
<title>LOGGING</title>
321
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.
325
361
<refsect1 id="exit_status">
326
362
<title>EXIT STATUS</title>
417
453
backtrace. This could be considered a feature.
420
Currently, if a client is declared <quote>invalid</quote> due to
421
having timed out, the server does not record this fact onto
422
permanent storage. This has some security implications, see
423
<xref linkend="CLIENTS"/>.
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"/>.
426
461
There is currently no way of querying the server of the current
434
469
Debug mode is conflated with running in the foreground.
437
The console log messages does not show a time stamp.
472
The console log messages do not show a time stamp.
440
475
This server does not check the expire time of clients’ OpenPGP
504
539
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
505
540
<manvolnum>5</manvolnum></citerefentry>)
506
541
<emphasis>must</emphasis> be made non-readable by anyone
507
except the user running the server.
542
except the user starting the server (usually root).
510
545
As detailed in <xref linkend="checking"/>, the status of all
515
550
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 <acronym>RAM</acronym> image of the client host. What
525
should be done in that case (if restarting the server program
526
really is necessary) is to stop the server program, edit the
527
configuration file to omit any suspect clients, and restart
551
by the server which would therefore disable the client. But
552
if the server was ever restarted, it would re-read its client
553
list from its configuration file and again regard all clients
554
therein as enabled, and hence eligible to receive their
555
passwords. Therefore, be careful when restarting servers if
556
it is suspected that a client has, in fact, been compromised
557
by parties who may now be running a fake Mandos client with
558
the keys from the non-encrypted initial <acronym>RAM</acronym>
559
image of the client host. What should be done in that case
560
(if restarting the server program really is necessary) is to
561
stop the server program, edit the configuration file to omit
562
any suspect clients, and restart the server program.
531
565
For more details on client-side security, see
532
<citerefentry><refentrytitle>password-request</refentrytitle>
566
<citerefentry><refentrytitle>mandos-client</refentrytitle>
533
567
<manvolnum>8mandos</manvolnum></citerefentry>.
538
572
<refsect1 id="see_also">
539
573
<title>SEE ALSO</title>
543
577
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
544
578
<refentrytitle>mandos.conf</refentrytitle>
545
579
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
546
<refentrytitle>password-request</refentrytitle>
580
<refentrytitle>mandos-client</refentrytitle>
547
581
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
548
582
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
added
removed
mandos.xml
