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
44
<holder>Teddy Hogeborn</holder>
37
45
<holder>Björn Påhlsson</holder>
87
95
<arg><option>--debug</option></arg>
97
<arg><option>--debuglevel
98
<replaceable>LEVEL</replaceable></option></arg>
100
<arg><option>--no-dbus</option></arg>
89
102
<arg><option>--no-ipv6</option></arg>
104
<arg><option>--no-restore</option></arg>
106
<arg><option>--statedir
107
<replaceable>DIRECTORY</replaceable></option></arg>
109
<arg><option>--socket
110
<replaceable>FD</replaceable></option></arg>
112
<arg><option>--foreground</option></arg>
114
<arg><option>--no-zeroconf</option></arg>
92
117
<command>&COMMANDNAME;</command>
111
136
<command>&COMMANDNAME;</command> is a server daemon which
112
137
handles incoming request for passwords for a pre-defined list of
113
client host computers. The Mandos server uses Zeroconf to
114
announce itself on the local network, and uses TLS to
115
communicate securely with and to authenticate the clients. The
116
Mandos server uses IPv6 to allow Mandos clients to use IPv6
117
link-local addresses, since the clients will probably not have
118
any other addresses configured (see <xref linkend="overview"/>).
119
Any authenticated client is then given the stored pre-encrypted
120
password for that specific client.
138
client host computers. For an introduction, see
139
<citerefentry><refentrytitle>intro</refentrytitle>
140
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
141
uses Zeroconf to announce itself on the local network, and uses
142
TLS to communicate securely with and to authenticate the
143
clients. The Mandos server uses IPv6 to allow Mandos clients to
144
use IPv6 link-local addresses, since the clients will probably
145
not have any other addresses configured (see <xref
146
linkend="overview"/>). Any authenticated client is then given
147
the stored pre-encrypted password for that specific client.
222
<term><option>--debuglevel
223
<replaceable>LEVEL</replaceable></option></term>
226
Set the debugging log level.
227
<replaceable>LEVEL</replaceable> is a string, one of
228
<quote><literal>CRITICAL</literal></quote>,
229
<quote><literal>ERROR</literal></quote>,
230
<quote><literal>WARNING</literal></quote>,
231
<quote><literal>INFO</literal></quote>, or
232
<quote><literal>DEBUG</literal></quote>, in order of
233
increasing verbosity. The default level is
234
<quote><literal>WARNING</literal></quote>.
195
240
<term><option>--priority <replaceable>
196
241
PRIORITY</replaceable></option></term>
281
<term><option>--no-dbus</option></term>
283
<xi:include href="mandos-options.xml" xpointer="dbus"/>
285
See also <xref linkend="dbus_interface"/>.
236
291
<term><option>--no-ipv6</option></term>
238
293
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
298
<term><option>--no-restore</option></term>
300
<xi:include href="mandos-options.xml" xpointer="restore"/>
302
See also <xref linkend="persistent_state"/>.
308
<term><option>--statedir
309
<replaceable>DIRECTORY</replaceable></option></term>
311
<xi:include href="mandos-options.xml" xpointer="statedir"/>
316
<term><option>--socket
317
<replaceable>FD</replaceable></option></term>
319
<xi:include href="mandos-options.xml" xpointer="socket"/>
324
<term><option>--foreground</option></term>
326
<xi:include href="mandos-options.xml"
327
xpointer="foreground"/>
332
<term><option>--no-zeroconf</option></term>
334
<xi:include href="mandos-options.xml" xpointer="zeroconf"/>
315
412
The server will, by default, continually check that the clients
316
413
are still up. If a client has not been confirmed as being up
317
414
for some time, the client is assumed to be compromised and is no
318
longer eligible to receive the encrypted password. The timeout,
319
checker program, and interval between checks can be configured
320
both globally and per client; see <citerefentry>
415
longer eligible to receive the encrypted password. (Manual
416
intervention is required to re-enable a client.) The timeout,
417
extended timeout, checker program, and interval between checks
418
can be configured both globally and per client; see
419
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
420
<manvolnum>5</manvolnum></citerefentry>.
424
<refsect1 id="approval">
425
<title>APPROVAL</title>
427
The server can be configured to require manual approval for a
428
client before it is sent its secret. The delay to wait for such
429
approval and the default action (approve or deny) can be
430
configured both globally and per client; see <citerefentry>
321
431
<refentrytitle>mandos-clients.conf</refentrytitle>
322
<manvolnum>5</manvolnum></citerefentry>.
432
<manvolnum>5</manvolnum></citerefentry>. By default all clients
433
will be approved immediately without delay.
436
This can be used to deny a client its secret if not manually
437
approved within a specified time. It can also be used to make
438
the server delay before giving a client its secret, allowing
439
optional manual denying of this specific client.
326
444
<refsect1 id="logging">
327
445
<title>LOGGING</title>
329
447
The server will send log message with various severity levels to
330
<filename>/dev/log</filename>. With the
448
<filename class="devicefile">/dev/log</filename>. With the
331
449
<option>--debug</option> option, it will log even more messages,
332
450
and also show them on the console.
454
<refsect1 id="persistent_state">
455
<title>PERSISTENT STATE</title>
457
Client settings, initially read from
458
<filename>clients.conf</filename>, are persistent across
459
restarts, and run-time changes will override settings in
460
<filename>clients.conf</filename>. However, if a setting is
461
<emphasis>changed</emphasis> (or a client added, or removed) in
462
<filename>clients.conf</filename>, this will take precedence.
466
<refsect1 id="dbus_interface">
467
<title>D-BUS INTERFACE</title>
469
The server will by default provide a D-Bus system bus interface.
470
This interface will only be accessible by the root user or a
471
Mandos-specific user, if such a user exists. For documentation
472
of the D-Bus API, see the file <filename>DBUS-API</filename>.
336
476
<refsect1 id="exit_status">
337
477
<title>EXIT STATUS</title>
393
<term><filename>/var/run/mandos.pid</filename></term>
396
The file containing the process id of
397
<command>&COMMANDNAME;</command>.
402
<term><filename>/dev/log</filename></term>
533
<term><filename>/run/mandos.pid</filename></term>
536
The file containing the process id of the
537
<command>&COMMANDNAME;</command> process started last.
538
<emphasis >Note:</emphasis> If the <filename
539
class="directory">/run</filename> directory does not
540
exist, <filename>/var/run/mandos.pid</filename> will be
547
class="directory">/var/lib/mandos</filename></term>
550
Directory where persistent state will be saved. Change
551
this with the <option>--statedir</option> option. See
552
also the <option>--no-restore</option> option.
557
<term><filename class="devicefile">/dev/log</filename></term>
405
560
The Unix domain socket to where local syslog messages are
428
583
backtrace. This could be considered a feature.
431
Currently, if a client is declared <quote>invalid</quote> due to
432
having timed out, the server does not record this fact onto
433
permanent storage. This has some security implications, see
434
<xref linkend="clients"/>.
437
There is currently no way of querying the server of the current
438
status of clients, other than analyzing its <systemitem
439
class="service">syslog</systemitem> output.
442
586
There is no fine-grained control over logging and debug output.
445
Debug mode is conflated with running in the foreground.
448
The console log messages do not show a time stamp.
451
589
This server does not check the expire time of clients’ OpenPGP
592
<xi:include href="bugs.xml"/>
456
595
<refsect1 id="example">
466
605
<informalexample>
468
607
Run the server in debug mode, read configuration files from
469
the <filename>~/mandos</filename> directory, and use the
470
Zeroconf service name <quote>Test</quote> to not collide with
471
any other official Mandos server on this host:
608
the <filename class="directory">~/mandos</filename> directory,
609
and use the Zeroconf service name <quote>Test</quote> to not
610
collide with any other official Mandos server on this host:
523
662
compromised if they are gone for too long.
526
If a client is compromised, its downtime should be duly noted
527
by the server which would therefore declare the client
528
invalid. But if the server was ever restarted, it would
529
re-read its client list from its configuration file and again
530
regard all clients therein as valid, and hence eligible to
531
receive their passwords. Therefore, be careful when
532
restarting servers if it is suspected that a client has, in
533
fact, been compromised by parties who may now be running a
534
fake Mandos client with the keys from the non-encrypted
535
initial <acronym>RAM</acronym> image of the client host. What
536
should be done in that case (if restarting the server program
537
really is necessary) is to stop the server program, edit the
538
configuration file to omit any suspect clients, and restart
542
665
For more details on client-side security, see
543
666
<citerefentry><refentrytitle>mandos-client</refentrytitle>
544
667
<manvolnum>8mandos</manvolnum></citerefentry>.
549
672
<refsect1 id="see_also">
550
673
<title>SEE ALSO</title>
553
<refentrytitle>mandos-clients.conf</refentrytitle>
554
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
555
<refentrytitle>mandos.conf</refentrytitle>
556
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
557
<refentrytitle>mandos-client</refentrytitle>
558
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
559
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
675
<citerefentry><refentrytitle>intro</refentrytitle>
676
<manvolnum>8mandos</manvolnum></citerefentry>,
677
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
678
<manvolnum>5</manvolnum></citerefentry>,
679
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
680
<manvolnum>5</manvolnum></citerefentry>,
681
<citerefentry><refentrytitle>mandos-client</refentrytitle>
682
<manvolnum>8mandos</manvolnum></citerefentry>,
683
<citerefentry><refentrytitle>sh</refentrytitle>
684
<manvolnum>1</manvolnum></citerefentry>
added
removed
mandos.xml
