26
26
specified IPv6 address. If a link-local address is specified, an
27
27
interface should be set, since a link-local address is only valid
28
28
on a single interface. By default, the server will listen to all
29
available addresses. If set, this must normally be an IPv6
30
address; an IPv4 address can only be specified using IPv4-mapped
31
IPv6 address syntax: <quote><systemitem class="ipaddress"
32
>::FFFF:192.0.2.3</systemitem ></quote>. (Only if IPv6 usage is
33
<emphasis>disabled</emphasis> (see below) must this be an IPv4
29
available addresses. If set, this must be an IPv6 address; an
30
IPv4 address can only be specified using IPv4-mapped IPv6 address
31
syntax: <quote><systemitem class="ipaddress"
32
>::FFFF:192.0.2.3</systemitem ></quote>.
49
47
<para id="priority">
50
GnuTLS priority string for the <acronym>TLS</acronym> handshake.
51
The default is <quote><literal
52
>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:!RSA</literal>
53
<literal>:+SIGN-DSA-SHA256</literal></quote>.
54
See <citerefentry><refentrytitle
55
>gnutls_priority_init</refentrytitle>
48
GnuTLS priority string for the <acronym>TLS</acronym> handshake
49
with the clients. The default is
50
<quote><literal>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal
51
></quote>. See <citerefentry>
52
<refentrytitle>gnutls_priority_init</refentrytitle>
56
53
<manvolnum>3</manvolnum></citerefentry> for the syntax.
57
54
<emphasis>Warning</emphasis>: changing this may make the
58
<acronym>TLS</acronym> handshake fail, making server-client
59
communication impossible. Changing this option may also make the
60
network traffic decryptable by an attacker.
55
<acronym>TLS</acronym> handshake fail, making communication with
63
59
<para id="servicename">
64
60
Zeroconf service name. The default is
65
61
<quote><literal>Mandos</literal></quote>. This only needs to be
66
changed if for some reason is would be necessary to run more than
67
one server on the same <emphasis>host</emphasis>. This would not
62
changed this if it, for some reason, is necessary to run more than
63
one server on the same <emphasis>host</emphasis>, which would not
68
64
normally be useful. If there are name collisions on the same
69
65
<emphasis>network</emphasis>, the newer server will automatically
70
66
rename itself to <quote><literal>Mandos #2</literal></quote>, and
71
67
so on; therefore, this option is not needed in that case.
75
This option controls whether the server will provide a D-Bus
76
system bus interface. The default is to provide such an
81
This option controls whether the server will use IPv6 sockets and
82
addresses. The default is to use IPv6. This option should
83
<emphasis>never</emphasis> normally be turned off, <emphasis>even in
84
IPv4-only environments</emphasis>. This is because <citerefentry>
85
<refentrytitle>mandos-client</refentrytitle>
86
<manvolnum>8mandos</manvolnum></citerefentry> will normally use
87
IPv6 link-local addresses, and will not be able to find or connect
88
to the server if this option is turned off. <emphasis>Only
89
advanced users should consider changing this option</emphasis>.
93
This option controls whether the server will restore its state
94
from the last time it ran. Default is to restore last state.
98
Directory to save (and restore) state in. Default is
100
class="directory">/var/lib/mandos</filename></quote>.
104
If this option is used, the server will not create a new network
105
socket, but will instead use the supplied file descriptor. By
106
default, the server will create a new network socket.
109
<para id="foreground">
110
This option will make the server run in the foreground and not
111
write a PID file. The default is to <emphasis>not</emphasis> run
112
in the foreground, except in <option>debug</option> mode, which
117
This option controls whether the server will announce its
118
existence using Zeroconf. Default is to use Zeroconf. If
119
Zeroconf is not used, a <option>port</option> number or a
120
<option>socket</option> is required.