19
19
<firstname>Björn</firstname>
20
20
<surname>Påhlsson</surname>
22
<email>belorn@recompile.se</email>
22
<email>belorn@fukt.bsnet.se</email>
26
26
<firstname>Teddy</firstname>
27
27
<surname>Hogeborn</surname>
29
<email>teddy@recompile.se</email>
29
<email>teddy@fukt.bsnet.se</email>
39
35
<holder>Teddy Hogeborn</holder>
40
36
<holder>Björn Påhlsson</holder>
88
84
<replaceable>DIRECTORY</replaceable></option></arg>
90
86
<arg><option>--debug</option></arg>
92
<arg><option>--debuglevel
93
<replaceable>LEVEL</replaceable></option></arg>
95
<arg><option>--no-dbus</option></arg>
97
<arg><option>--no-ipv6</option></arg>
99
<arg><option>--no-restore</option></arg>
101
<arg><option>--statedir
102
<replaceable>DIRECTORY</replaceable></option></arg>
104
<arg><option>--socket
105
<replaceable>FD</replaceable></option></arg>
107
<arg><option>--foreground</option></arg>
110
89
<command>&COMMANDNAME;</command>
129
108
<command>&COMMANDNAME;</command> is a server daemon which
130
109
handles incoming request for passwords for a pre-defined list of
131
client host computers. For an introduction, see
132
<citerefentry><refentrytitle>intro</refentrytitle>
133
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
134
uses Zeroconf to announce itself on the local network, and uses
135
TLS to communicate securely with and to authenticate the
136
clients. The Mandos server uses IPv6 to allow Mandos clients to
137
use IPv6 link-local addresses, since the clients will probably
138
not have any other addresses configured (see <xref
139
linkend="overview"/>). Any authenticated client is then given
140
the stored pre-encrypted password for that specific client.
110
client host computers. The Mandos server uses Zeroconf to
111
announce itself on the local network, and uses TLS to
112
communicate securely with and to authenticate the clients. The
113
Mandos server uses IPv6 to allow Mandos clients to use IPv6
114
link-local addresses, since the clients will probably not have
115
any other addresses configured (see <xref linkend="overview"/>).
116
Any authenticated client is then given the stored pre-encrypted
117
password for that specific client.
215
<term><option>--debuglevel
216
<replaceable>LEVEL</replaceable></option></term>
219
Set the debugging log level.
220
<replaceable>LEVEL</replaceable> is a string, one of
221
<quote><literal>CRITICAL</literal></quote>,
222
<quote><literal>ERROR</literal></quote>,
223
<quote><literal>WARNING</literal></quote>,
224
<quote><literal>INFO</literal></quote>, or
225
<quote><literal>DEBUG</literal></quote>, in order of
226
increasing verbosity. The default level is
227
<quote><literal>WARNING</literal></quote>.
233
192
<term><option>--priority <replaceable>
234
193
PRIORITY</replaceable></option></term>
274
<term><option>--no-dbus</option></term>
276
<xi:include href="mandos-options.xml" xpointer="dbus"/>
278
See also <xref linkend="dbus_interface"/>.
284
<term><option>--no-ipv6</option></term>
286
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
291
<term><option>--no-restore</option></term>
293
<xi:include href="mandos-options.xml" xpointer="restore"/>
295
See also <xref linkend="persistent_state"/>.
301
<term><option>--statedir
302
<replaceable>DIRECTORY</replaceable></option></term>
304
<xi:include href="mandos-options.xml" xpointer="statedir"/>
309
<term><option>--socket
310
<replaceable>FD</replaceable></option></term>
312
<xi:include href="mandos-options.xml" xpointer="socket"/>
317
<term><option>--foreground</option></term>
319
<xi:include href="mandos-options.xml"
320
xpointer="foreground"/>
398
305
The server will, by default, continually check that the clients
399
306
are still up. If a client has not been confirmed as being up
400
307
for some time, the client is assumed to be compromised and is no
401
longer eligible to receive the encrypted password. (Manual
402
intervention is required to re-enable a client.) The timeout,
403
extended timeout, checker program, and interval between checks
404
can be configured both globally and per client; see
405
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
308
longer eligible to receive the encrypted password. The timeout,
309
checker program, and interval between checks can be configured
310
both globally and per client; see <citerefentry>
311
<refentrytitle>mandos-clients.conf</refentrytitle>
406
312
<manvolnum>5</manvolnum></citerefentry>.
410
<refsect1 id="approval">
411
<title>APPROVAL</title>
413
The server can be configured to require manual approval for a
414
client before it is sent its secret. The delay to wait for such
415
approval and the default action (approve or deny) can be
416
configured both globally and per client; see <citerefentry>
417
<refentrytitle>mandos-clients.conf</refentrytitle>
418
<manvolnum>5</manvolnum></citerefentry>. By default all clients
419
will be approved immediately without delay.
422
This can be used to deny a client its secret if not manually
423
approved within a specified time. It can also be used to make
424
the server delay before giving a client its secret, allowing
425
optional manual denying of this specific client.
430
316
<refsect1 id="logging">
431
317
<title>LOGGING</title>
433
319
The server will send log message with various severity levels to
434
<filename class="devicefile">/dev/log</filename>. With the
320
<filename>/dev/log</filename>. With the
435
321
<option>--debug</option> option, it will log even more messages,
436
322
and also show them on the console.
440
<refsect1 id="persistent_state">
441
<title>PERSISTENT STATE</title>
443
Client settings, initially read from
444
<filename>clients.conf</filename>, are persistent across
445
restarts, and run-time changes will override settings in
446
<filename>clients.conf</filename>. However, if a setting is
447
<emphasis>changed</emphasis> (or a client added, or removed) in
448
<filename>clients.conf</filename>, this will take precedence.
452
<refsect1 id="dbus_interface">
453
<title>D-BUS INTERFACE</title>
455
The server will by default provide a D-Bus system bus interface.
456
This interface will only be accessible by the root user or a
457
Mandos-specific user, if such a user exists. For documentation
458
of the D-Bus API, see the file <filename>DBUS-API</filename>.
462
326
<refsect1 id="exit_status">
463
327
<title>EXIT STATUS</title>
519
383
<term><filename>/var/run/mandos.pid</filename></term>
522
The file containing the process id of the
523
<command>&COMMANDNAME;</command> process started last.
528
<term><filename class="devicefile">/dev/log</filename></term>
532
class="directory">/var/lib/mandos</filename></term>
535
Directory where persistent state will be saved. Change
536
this with the <option>--statedir</option> option. See
537
also the <option>--no-restore</option> option.
386
The file containing the process id of
387
<command>&COMMANDNAME;</command>.
568
418
backtrace. This could be considered a feature.
421
Currently, if a client is declared <quote>invalid</quote> due to
422
having timed out, the server does not record this fact onto
423
permanent storage. This has some security implications, see
424
<xref linkend="CLIENTS"/>.
427
There is currently no way of querying the server of the current
428
status of clients, other than analyzing its <systemitem
429
class="service">syslog</systemitem> output.
571
432
There is no fine-grained control over logging and debug output.
435
Debug mode is conflated with running in the foreground.
438
The console log messages does not show a time stamp.
574
441
This server does not check the expire time of clients’ OpenPGP
589
456
<informalexample>
591
458
Run the server in debug mode, read configuration files from
592
the <filename class="directory">~/mandos</filename> directory,
593
and use the Zeroconf service name <quote>Test</quote> to not
594
collide with any other official Mandos server on this host:
459
the <filename>~/mandos</filename> directory, and use the
460
Zeroconf service name <quote>Test</quote> to not collide with
461
any other official Mandos server on this host:
646
513
compromised if they are gone for too long.
516
If a client is compromised, its downtime should be duly noted
517
by the server which would therefore declare the client
518
invalid. But if the server was ever restarted, it would
519
re-read its client list from its configuration file and again
520
regard all clients therein as valid, and hence eligible to
521
receive their passwords. Therefore, be careful when
522
restarting servers if it is suspected that a client has, in
523
fact, been compromised by parties who may now be running a
524
fake Mandos client with the keys from the non-encrypted
525
initial <acronym>RAM</acronym> image of the client host. What
526
should be done in that case (if restarting the server program
527
really is necessary) is to stop the server program, edit the
528
configuration file to omit any suspect clients, and restart
649
532
For more details on client-side security, see
650
533
<citerefentry><refentrytitle>mandos-client</refentrytitle>
651
534
<manvolnum>8mandos</manvolnum></citerefentry>.
656
539
<refsect1 id="see_also">
657
540
<title>SEE ALSO</title>
659
<citerefentry><refentrytitle>intro</refentrytitle>
660
<manvolnum>8mandos</manvolnum></citerefentry>,
661
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
662
<manvolnum>5</manvolnum></citerefentry>,
663
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
664
<manvolnum>5</manvolnum></citerefentry>,
665
<citerefentry><refentrytitle>mandos-client</refentrytitle>
666
<manvolnum>8mandos</manvolnum></citerefentry>,
667
<citerefentry><refentrytitle>sh</refentrytitle>
668
<manvolnum>1</manvolnum></citerefentry>
543
<refentrytitle>mandos-clients.conf</refentrytitle>
544
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
545
<refentrytitle>mandos.conf</refentrytitle>
546
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
547
<refentrytitle>mandos-client</refentrytitle>
548
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
549
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
added
removed
mandos.xml
