19
19
<firstname>Björn</firstname>
20
20
<surname>Påhlsson</surname>
22
<email>belorn@fukt.bsnet.se</email>
22
<email>belorn@recompile.se</email>
26
26
<firstname>Teddy</firstname>
27
27
<surname>Hogeborn</surname>
29
<email>teddy@fukt.bsnet.se</email>
29
<email>teddy@recompile.se</email>
36
39
<holder>Teddy Hogeborn</holder>
37
40
<holder>Björn Påhlsson</holder>
87
90
<arg><option>--debug</option></arg>
92
<arg><option>--debuglevel
93
<replaceable>LEVEL</replaceable></option></arg>
89
95
<arg><option>--no-dbus</option></arg>
91
97
<arg><option>--no-ipv6</option></arg>
99
<arg><option>--no-restore</option></arg>
101
<arg><option>--statedir
102
<replaceable>DIRECTORY</replaceable></option></arg>
94
105
<command>&COMMANDNAME;</command>
113
124
<command>&COMMANDNAME;</command> is a server daemon which
114
125
handles incoming request for passwords for a pre-defined list of
115
client host computers. The Mandos server uses Zeroconf to
116
announce itself on the local network, and uses TLS to
117
communicate securely with and to authenticate the clients. The
118
Mandos server uses IPv6 to allow Mandos clients to use IPv6
119
link-local addresses, since the clients will probably not have
120
any other addresses configured (see <xref linkend="overview"/>).
121
Any authenticated client is then given the stored pre-encrypted
122
password for that specific client.
126
client host computers. For an introduction, see
127
<citerefentry><refentrytitle>intro</refentrytitle>
128
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
129
uses Zeroconf to announce itself on the local network, and uses
130
TLS to communicate securely with and to authenticate the
131
clients. The Mandos server uses IPv6 to allow Mandos clients to
132
use IPv6 link-local addresses, since the clients will probably
133
not have any other addresses configured (see <xref
134
linkend="overview"/>). Any authenticated client is then given
135
the stored pre-encrypted password for that specific client.
210
<term><option>--debuglevel
211
<replaceable>LEVEL</replaceable></option></term>
214
Set the debugging log level.
215
<replaceable>LEVEL</replaceable> is a string, one of
216
<quote><literal>CRITICAL</literal></quote>,
217
<quote><literal>ERROR</literal></quote>,
218
<quote><literal>WARNING</literal></quote>,
219
<quote><literal>INFO</literal></quote>, or
220
<quote><literal>DEBUG</literal></quote>, in order of
221
increasing verbosity. The default level is
222
<quote><literal>WARNING</literal></quote>.
197
228
<term><option>--priority <replaceable>
198
229
PRIORITY</replaceable></option></term>
327
376
The server will, by default, continually check that the clients
328
377
are still up. If a client has not been confirmed as being up
329
378
for some time, the client is assumed to be compromised and is no
330
longer eligible to receive the encrypted password. The timeout,
331
checker program, and interval between checks can be configured
332
both globally and per client; see <citerefentry>
379
longer eligible to receive the encrypted password. (Manual
380
intervention is required to re-enable a client.) The timeout,
381
extended timeout, checker program, and interval between checks
382
can be configured both globally and per client; see
383
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
384
<manvolnum>5</manvolnum></citerefentry>.
388
<refsect1 id="approval">
389
<title>APPROVAL</title>
391
The server can be configured to require manual approval for a
392
client before it is sent its secret. The delay to wait for such
393
approval and the default action (approve or deny) can be
394
configured both globally and per client; see <citerefentry>
333
395
<refentrytitle>mandos-clients.conf</refentrytitle>
334
<manvolnum>5</manvolnum></citerefentry>.
396
<manvolnum>5</manvolnum></citerefentry>. By default all clients
397
will be approved immediately without delay.
400
This can be used to deny a client its secret if not manually
401
approved within a specified time. It can also be used to make
402
the server delay before giving a client its secret, allowing
403
optional manual denying of this specific client.
338
408
<refsect1 id="logging">
339
409
<title>LOGGING</title>
341
411
The server will send log message with various severity levels to
342
<filename>/dev/log</filename>. With the
412
<filename class="devicefile">/dev/log</filename>. With the
343
413
<option>--debug</option> option, it will log even more messages,
344
414
and also show them on the console.
418
<refsect1 id="persistent_state">
419
<title>PERSISTENT STATE</title>
421
Client settings, initially read from
422
<filename>clients.conf</filename>, are persistent across
423
restarts, and run-time changes will override settings in
424
<filename>clients.conf</filename>. However, if a setting is
425
<emphasis>changed</emphasis> (or a client added, or removed) in
426
<filename>clients.conf</filename>, this will take precedence.
348
430
<refsect1 id="dbus_interface">
349
431
<title>D-BUS INTERFACE</title>
351
433
The server will by default provide a D-Bus system bus interface.
352
434
This interface will only be accessible by the root user or a
353
Mandos-specific user, if such a user exists.
435
Mandos-specific user, if such a user exists. For documentation
436
of the D-Bus API, see the file <filename>DBUS-API</filename>.
415
497
<term><filename>/var/run/mandos.pid</filename></term>
418
The file containing the process id of
419
<command>&COMMANDNAME;</command>.
500
The file containing the process id of the
501
<command>&COMMANDNAME;</command> process started last.
506
<term><filename class="devicefile">/dev/log</filename></term>
510
class="directory">/var/lib/mandos</filename></term>
513
Directory where persistent state will be saved. Change
514
this with the <option>--statedir</option> option. See
515
also the <option>--no-restore</option> option.
450
546
backtrace. This could be considered a feature.
453
Currently, if a client is declared <quote>invalid</quote> due to
454
having timed out, the server does not record this fact onto
455
permanent storage. This has some security implications, see
456
<xref linkend="clients"/>.
459
There is currently no way of querying the server of the current
460
status of clients, other than analyzing its <systemitem
461
class="service">syslog</systemitem> output.
464
549
There is no fine-grained control over logging and debug output.
467
552
Debug mode is conflated with running in the foreground.
470
The console log messages does not show a time stamp.
473
555
This server does not check the expire time of clients’ OpenPGP
488
570
<informalexample>
490
572
Run the server in debug mode, read configuration files from
491
the <filename>~/mandos</filename> directory, and use the
492
Zeroconf service name <quote>Test</quote> to not collide with
493
any other official Mandos server on this host:
573
the <filename class="directory">~/mandos</filename> directory,
574
and use the Zeroconf service name <quote>Test</quote> to not
575
collide with any other official Mandos server on this host:
545
627
compromised if they are gone for too long.
548
If a client is compromised, its downtime should be duly noted
549
by the server which would therefore declare the client
550
invalid. But if the server was ever restarted, it would
551
re-read its client list from its configuration file and again
552
regard all clients therein as valid, and hence eligible to
553
receive their passwords. Therefore, be careful when
554
restarting servers if it is suspected that a client has, in
555
fact, been compromised by parties who may now be running a
556
fake Mandos client with the keys from the non-encrypted
557
initial <acronym>RAM</acronym> image of the client host. What
558
should be done in that case (if restarting the server program
559
really is necessary) is to stop the server program, edit the
560
configuration file to omit any suspect clients, and restart
564
630
For more details on client-side security, see
565
631
<citerefentry><refentrytitle>mandos-client</refentrytitle>
566
632
<manvolnum>8mandos</manvolnum></citerefentry>.
571
637
<refsect1 id="see_also">
572
638
<title>SEE ALSO</title>
575
<refentrytitle>mandos-clients.conf</refentrytitle>
576
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
577
<refentrytitle>mandos.conf</refentrytitle>
578
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
579
<refentrytitle>mandos-client</refentrytitle>
580
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
581
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
640
<citerefentry><refentrytitle>intro</refentrytitle>
641
<manvolnum>8mandos</manvolnum></citerefentry>,
642
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
643
<manvolnum>5</manvolnum></citerefentry>,
644
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
645
<manvolnum>5</manvolnum></citerefentry>,
646
<citerefentry><refentrytitle>mandos-client</refentrytitle>
647
<manvolnum>8mandos</manvolnum></citerefentry>,
648
<citerefentry><refentrytitle>sh</refentrytitle>
649
<manvolnum>1</manvolnum></citerefentry>
added
removed
mandos.xml
