17
15
and listen to requests on the specified network interface.
18
16
Default is to use all available interfaces. <emphasis
19
17
>Note:</emphasis> a failure to bind to the specified
20
interface is not considered critical, and the server will not
21
exit, but instead continue normally.
18
interface is not considered critical, and the server does not
19
exit, but will instead continue normally.
24
22
<para id="address">
26
24
specified IPv6 address. If a link-local address is specified, an
27
25
interface should be set, since a link-local address is only valid
28
26
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
27
available addresses. If set, this must be an IPv6 address; an
28
IPv4 address can only be specified using IPv4-mapped IPv6 address
29
syntax: <quote><systemitem class="ipaddress"
30
>::FFFF:192.0.2.3</systemitem ></quote>.
49
45
<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</literal></quote>. See
53
<citerefentry><refentrytitle>gnutls_priority_init</refentrytitle>
46
GnuTLS priority string for the <acronym>TLS</acronym> handshake
47
with the clients. The default is
48
<quote><literal>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal
49
></quote>. See <citerefentry>
50
<refentrytitle>gnutls_priority_init</refentrytitle>
54
51
<manvolnum>3</manvolnum></citerefentry> for the syntax.
55
52
<emphasis>Warning</emphasis>: changing this may make the
56
<acronym>TLS</acronym> handshake fail, making server-client
57
communication impossible.
53
<acronym>TLS</acronym> handshake fail, making communication with
60
57
<para id="servicename">
61
58
Zeroconf service name. The default is
62
59
<quote><literal>Mandos</literal></quote>. This only needs to be
63
changed if for some reason is would be necessary to run more than
64
one server on the same <emphasis>host</emphasis>. This would not
60
changed this if it, for some reason, is necessary to run more than
61
one server on the same <emphasis>host</emphasis>, which would not
65
62
normally be useful. If there are name collisions on the same
66
63
<emphasis>network</emphasis>, the newer server will automatically
67
64
rename itself to <quote><literal>Mandos #2</literal></quote>, and
68
65
so on; therefore, this option is not needed in that case.
72
This option controls whether the server will provide a D-Bus
73
system bus interface. The default is to provide such an
78
This option controls whether the server will use IPv6 sockets and
79
addresses. The default is to use IPv6. This option should
80
<emphasis>never</emphasis> normally be turned off, <emphasis>even in
81
IPv4-only environments</emphasis>. This is because <citerefentry>
82
<refentrytitle>mandos-client</refentrytitle>
83
<manvolnum>8mandos</manvolnum></citerefentry> will normally use
84
IPv6 link-local addresses, and will not be able to find or connect
85
to the server if this option is turned off. <emphasis>Only
86
advanced users should consider changing this option</emphasis>.
90
This option controls whether the server will restore its state
91
from the last time it ran. Default is to restore last state.
95
Directory to save (and restore) state in. Default is
97
class="directory">/var/lib/mandos</filename></quote>.
101
If this option is used, the server will not create a new network
102
socket, but will instead use the supplied file descriptor. By
103
default, the server will create a new network socket.