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
48
GnuTLS priority string for the <acronym>TLS</acronym> handshake.
52
<quote><literal>SECURE128​:!CTYPE-X.509​:+CTYPE-RAWPK​:!RSA​:!VERS-ALL​:+VERS-TLS1.3​:%PROFILE_ULTRA</literal></quote>
53
when using raw public keys in TLS, and
54
<quote><literal>SECURE256​:!CTYPE-X.509​:+CTYPE-OPENPGP​:!RSA​:+SIGN-DSA-SHA256</literal></quote>
55
when using OpenPGP keys in TLS,. See <citerefentry><refentrytitle
56
>gnutls_priority_init</refentrytitle>
49
The default is <quote><literal
50
>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal></quote>. See
51
<citerefentry><refentrytitle>gnutls_priority_init</refentrytitle>
57
52
<manvolnum>3</manvolnum></citerefentry> for the syntax.
58
53
<emphasis>Warning</emphasis>: changing this may make the
59
54
<acronym>TLS</acronym> handshake fail, making server-client
60
communication impossible. Changing this option may also make the
61
network traffic decryptable by an attacker.
55
communication impossible.
64
58
<para id="servicename">
65
59
Zeroconf service name. The default is
66
60
<quote><literal>Mandos</literal></quote>. This only needs to be
67
changed if for some reason is would be necessary to run more than
68
one server on the same <emphasis>host</emphasis>. This would not
61
changed this if it, for some reason, is necessary to run more than
62
one server on the same <emphasis>host</emphasis>, which would not
69
63
normally be useful. If there are name collisions on the same
70
64
<emphasis>network</emphasis>, the newer server will automatically
71
65
rename itself to <quote><literal>Mandos #2</literal></quote>, and
72
66
so on; therefore, this option is not needed in that case.
76
This option controls whether the server will provide a D-Bus
77
system bus interface. The default is to provide such an
82
This option controls whether the server will use IPv6 sockets and
83
addresses. The default is to use IPv6. This option should
84
<emphasis>never</emphasis> normally be turned off, <emphasis>even in
85
IPv4-only environments</emphasis>. This is because <citerefentry>
86
<refentrytitle>mandos-client</refentrytitle>
87
<manvolnum>8mandos</manvolnum></citerefentry> will normally use
88
IPv6 link-local addresses, and will not be able to find or connect
89
to the server if this option is turned off. <emphasis>Only
90
advanced users should consider changing this option</emphasis>.
94
This option controls whether the server will restore its state
95
from the last time it ran. Default is to restore last state.
99
Directory to save (and restore) state in. Default is
101
class="directory">/var/lib/mandos</filename></quote>.
105
If this option is used, the server will not create a new network
106
socket, but will instead use the supplied file descriptor. By
107
default, the server will create a new network socket.
110
<para id="foreground">
111
This option will make the server run in the foreground and not
112
write a PID file. The default is to <emphasis>not</emphasis> run
113
in the foreground, except in <option>debug</option> mode, which
118
This option controls whether the server will announce its
119
existence using Zeroconf. Default is to use Zeroconf. If
120
Zeroconf is not used, a <option>port</option> number or a
121
<option>socket</option> is required.
added
removed
mandos-options.xml
