68
58
<refname><command>&COMMANDNAME;</command></refname>
70
Sends encrypted passwords to authenticated Mandos clients
60
Gives encrypted passwords to authenticated Mandos clients
76
66
<command>&COMMANDNAME;</command>
77
<arg choice='opt'>--interface<arg choice='plain'>IF</arg></arg>
78
<arg choice='opt'>--address<arg choice='plain'>ADDRESS</arg></arg>
79
<arg choice='opt'>--port<arg choice='plain'>PORT</arg></arg>
80
<arg choice='opt'>--priority<arg choice='plain'>PRIORITY</arg></arg>
81
<arg choice='opt'>--servicename<arg choice='plain'>NAME</arg></arg>
82
<arg choice='opt'>--configdir<arg choice='plain'>DIRECTORY</arg></arg>
83
<arg choice='opt'>--debug</arg>
86
<command>&COMMANDNAME;</command>
87
<arg choice='opt'>-i<arg choice='plain'>IF</arg></arg>
88
<arg choice='opt'>-a<arg choice='plain'>ADDRESS</arg></arg>
89
<arg choice='opt'>-p<arg choice='plain'>PORT</arg></arg>
90
<arg choice='opt'>--priority<arg choice='plain'>PRIORITY</arg></arg>
91
<arg choice='opt'>--servicename<arg choice='plain'>NAME</arg></arg>
92
<arg choice='opt'>--configdir<arg choice='plain'>DIRECTORY</arg></arg>
93
<arg choice='opt'>--debug</arg>
96
<command>&COMMANDNAME;</command>
97
<arg choice='plain'>--help</arg>
100
<command>&COMMANDNAME;</command>
101
<arg choice='plain'>--version</arg>
104
<command>&COMMANDNAME;</command>
105
<arg choice='plain'>--check</arg>
68
<arg choice="plain"><option>--interface
69
<replaceable>NAME</replaceable></option></arg>
70
<arg choice="plain"><option>-i
71
<replaceable>NAME</replaceable></option></arg>
75
<arg choice="plain"><option>--address
76
<replaceable>ADDRESS</replaceable></option></arg>
77
<arg choice="plain"><option>-a
78
<replaceable>ADDRESS</replaceable></option></arg>
82
<arg choice="plain"><option>--port
83
<replaceable>PORT</replaceable></option></arg>
84
<arg choice="plain"><option>-p
85
<replaceable>PORT</replaceable></option></arg>
88
<arg><option>--priority
89
<replaceable>PRIORITY</replaceable></option></arg>
91
<arg><option>--servicename
92
<replaceable>NAME</replaceable></option></arg>
94
<arg><option>--configdir
95
<replaceable>DIRECTORY</replaceable></option></arg>
97
<arg><option>--debug</option></arg>
99
<arg><option>--debuglevel
100
<replaceable>LEVEL</replaceable></option></arg>
102
<arg><option>--no-dbus</option></arg>
104
<arg><option>--no-ipv6</option></arg>
106
<arg><option>--no-restore</option></arg>
108
<arg><option>--statedir
109
<replaceable>DIRECTORY</replaceable></option></arg>
111
<arg><option>--socket
112
<replaceable>FD</replaceable></option></arg>
114
<arg><option>--foreground</option></arg>
116
<arg><option>--no-zeroconf</option></arg>
119
<command>&COMMANDNAME;</command>
121
<arg choice="plain"><option>--help</option></arg>
122
<arg choice="plain"><option>-h</option></arg>
126
<command>&COMMANDNAME;</command>
127
<arg choice="plain"><option>--version</option></arg>
130
<command>&COMMANDNAME;</command>
131
<arg choice="plain"><option>--check</option></arg>
107
133
</refsynopsisdiv>
109
135
<refsect1 id="description">
110
136
<title>DESCRIPTION</title>
112
138
<command>&COMMANDNAME;</command> is a server daemon which
113
139
handles incoming request for passwords for a pre-defined list of
114
client host computers. The Mandos server uses Zeroconf to
115
announce itself on the local network, and uses GnuTLS to
116
communicate securely with and to authenticate the clients.
117
Mandos uses IPv6 link-local addresses, since the clients are
118
assumed to not have any other addresses configured yet. Any
119
authenticated client is then given the pre-encrypted password
120
for that specific client.
140
client host computers. For an introduction, see
141
<citerefentry><refentrytitle>intro</refentrytitle>
142
<manvolnum>8mandos</manvolnum></citerefentry>. The Mandos server
143
uses Zeroconf to announce itself on the local network, and uses
144
TLS to communicate securely with and to authenticate the
145
clients. The Mandos server uses IPv6 to allow Mandos clients to
146
use IPv6 link-local addresses, since the clients will probably
147
not have any other addresses configured (see <xref
148
linkend="overview"/>). Any authenticated client is then given
149
the stored pre-encrypted password for that specific client.
125
153
<refsect1 id="purpose">
126
154
<title>PURPOSE</title>
129
156
The purpose of this is to enable <emphasis>remote and unattended
130
rebooting</emphasis> of any client host computer with an
131
<emphasis>encrypted root file system</emphasis>. The client
132
host computer should start a Mandos client in the initial RAM
133
disk environment, the Mandos client program communicates with
134
this server program to get an encrypted password, which is then
135
decrypted and used to unlock the encrypted root file system.
136
The client host computer can then continue its boot sequence
157
rebooting</emphasis> of client host computer with an
158
<emphasis>encrypted root file system</emphasis>. See <xref
159
linkend="overview"/> for details.
142
163
<refsect1 id="options">
143
164
<title>OPTIONS</title>
147
<term><literal>-h</literal>, <literal>--help</literal></term>
167
<term><option>--help</option></term>
168
<term><option>-h</option></term>
150
171
Show a help message and exit
156
<term><literal>-i</literal>, <literal>--interface <replaceable>
157
IF</replaceable></literal></term>
160
Only announce the server and listen to requests on network
161
interface <replaceable>IF</replaceable>. Default is to
162
use all available interfaces.
168
<term><literal>-a</literal>, <literal>--address <replaceable>
169
ADDRESS</replaceable></literal></term>
172
If this option is used, the server will only listen to a
173
specific address. This must currently be an IPv6 address;
174
an IPv4 address can be specified using the
175
"<literal>::FFFF:192.0.2.3</literal>" syntax. Also, if a
176
link-local address is specified, an interface should be
177
set, since a link-local address is only valid on a single
178
interface. By default, the server will listen to all
185
<term><literal>-p</literal>, <literal>--port <replaceable>
186
PORT</replaceable></literal></term>
189
If this option is used, the server to bind to that
190
port. By default, the server will listen to an arbitrary
191
port given by the operating system.
197
<term><literal>--check</literal></term>
200
Run the server's self-tests. This includes any unit
177
<term><option>--interface</option>
178
<replaceable>NAME</replaceable></term>
179
<term><option>-i</option>
180
<replaceable>NAME</replaceable></term>
182
<xi:include href="mandos-options.xml" xpointer="interface"/>
187
<term><option>--address
188
<replaceable>ADDRESS</replaceable></option></term>
190
<replaceable>ADDRESS</replaceable></option></term>
192
<xi:include href="mandos-options.xml" xpointer="address"/>
198
<replaceable>PORT</replaceable></option></term>
200
<replaceable>PORT</replaceable></option></term>
202
<xi:include href="mandos-options.xml" xpointer="port"/>
207
<term><option>--check</option></term>
210
Run the server’s self-tests. This includes any unit
207
<term><literal>--debug</literal></term>
210
If the server is run in debug mode, it will run in the
211
foreground and print a lot of debugging information. The
212
default is <emphasis>not</emphasis> to run in debug mode.
218
<term><literal>--priority <replaceable>
219
PRIORITY</replaceable></literal></term>
222
GnuTLS priority string for the TLS handshake with the
224
<citerefentry><refentrytitle>gnutls_priority_init
225
</refentrytitle><manvolnum>3</manvolnum></citerefentry>
226
for the syntax. The default is
227
"<literal>SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal>".
228
<emphasis>Warning</emphasis>: changing this may make the
229
TLS handshake fail, making communication with clients
236
<term><literal>--servicename <replaceable>NAME</replaceable>
240
Zeroconf service name. The default is
241
"<literal>Mandos</literal>". You only need to change this
242
if you for some reason want to run more than one server on
243
the same <emphasis>host</emphasis>. If there are name
244
collisions on the same <emphasis>network</emphasis>, the
245
new server will automatically rename itself to "Mandos
252
<term><literal>--configdir <replaceable>DIR</replaceable>
217
<term><option>--debug</option></term>
219
<xi:include href="mandos-options.xml" xpointer="debug"/>
224
<term><option>--debuglevel
225
<replaceable>LEVEL</replaceable></option></term>
228
Set the debugging log level.
229
<replaceable>LEVEL</replaceable> is a string, one of
230
<quote><literal>CRITICAL</literal></quote>,
231
<quote><literal>ERROR</literal></quote>,
232
<quote><literal>WARNING</literal></quote>,
233
<quote><literal>INFO</literal></quote>, or
234
<quote><literal>DEBUG</literal></quote>, in order of
235
increasing verbosity. The default level is
236
<quote><literal>WARNING</literal></quote>.
242
<term><option>--priority <replaceable>
243
PRIORITY</replaceable></option></term>
245
<xi:include href="mandos-options.xml" xpointer="priority"/>
250
<term><option>--servicename
251
<replaceable>NAME</replaceable></option></term>
253
<xi:include href="mandos-options.xml"
254
xpointer="servicename"/>
259
<term><option>--configdir
260
<replaceable>DIRECTORY</replaceable></option></term>
256
263
Directory to search for configuration files. Default is
257
"<literal>/etc/mandos</literal>". See <citerefentry>
258
<refentrytitle>mandos.conf</refentrytitle>
264
<quote><literal>/etc/mandos</literal></quote>. See
265
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
259
266
<manvolnum>5</manvolnum></citerefentry> and <citerefentry>
260
267
<refentrytitle>mandos-clients.conf</refentrytitle>
261
268
<manvolnum>5</manvolnum></citerefentry>.
267
<term><literal>--version</literal></term>
274
<term><option>--version</option></term>
270
277
Prints the program version and exit.
283
<term><option>--no-dbus</option></term>
285
<xi:include href="mandos-options.xml" xpointer="dbus"/>
287
See also <xref linkend="dbus_interface"/>.
293
<term><option>--no-ipv6</option></term>
295
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
300
<term><option>--no-restore</option></term>
302
<xi:include href="mandos-options.xml" xpointer="restore"/>
304
See also <xref linkend="persistent_state"/>.
310
<term><option>--statedir
311
<replaceable>DIRECTORY</replaceable></option></term>
313
<xi:include href="mandos-options.xml" xpointer="statedir"/>
318
<term><option>--socket
319
<replaceable>FD</replaceable></option></term>
321
<xi:include href="mandos-options.xml" xpointer="socket"/>
326
<term><option>--foreground</option></term>
328
<xi:include href="mandos-options.xml"
329
xpointer="foreground"/>
334
<term><option>--no-zeroconf</option></term>
336
<xi:include href="mandos-options.xml" xpointer="zeroconf"/>
343
<refsect1 id="overview">
344
<title>OVERVIEW</title>
345
<xi:include href="overview.xml"/>
347
This program is the server part. It is a normal server program
348
and will run in a normal system environment, not in an initial
349
<acronym>RAM</acronym> disk environment.
277
353
<refsect1 id="protocol">
278
354
<title>NETWORK PROTOCOL</title>
280
356
The Mandos server announces itself as a Zeroconf service of type
281
"<literal>_mandos._tcp</literal>". The Mandos client connects
282
to the announced address and port, and sends a line of text
283
where the first whitespace-separated field is the protocol
284
version, which currently is "<literal>1</literal>". The client
285
and server then start a TLS protocol handshake with a slight
286
quirk: the Mandos server program acts as a TLS "client" while
287
the connecting Mandos client acts as a TLS "server". The Mandos
288
client must supply an OpenPGP certificate, and the fingerprint
289
of this certificate is used by the Mandos server to look up (in
290
a list read from a file at start time) which binary blob to give
291
the client. No other authentication or authorization is done by
357
<quote><literal>_mandos._tcp</literal></quote>. The Mandos
358
client connects to the announced address and port, and sends a
359
line of text where the first whitespace-separated field is the
360
protocol version, which currently is
361
<quote><literal>1</literal></quote>. The client and server then
362
start a TLS protocol handshake with a slight quirk: the Mandos
363
server program acts as a TLS <quote>client</quote> while the
364
connecting Mandos client acts as a TLS <quote>server</quote>.
365
The Mandos client must supply a TLS public key, and the key ID
366
of this public key is used by the Mandos server to look up (in a
367
list read from <filename>clients.conf</filename> at start time)
368
which binary blob to give the client. No other authentication
369
or authorization is done by the server.
294
<informaltable><tgroup cols="3"><thead>
372
<title>Mandos Protocol (Version 1)</title><tgroup cols="3"><thead>
296
374
<entry>Mandos Client</entry>
297
375
<entry>Direction</entry>
303
381
<entry>-><!-- → --></entry>
306
<entry>"<literal>1\r\en</literal>"</entry>
384
<entry><quote><literal>1\r\n</literal></quote></entry>
307
385
<entry>-><!-- → --></entry>
310
<entry>TLS handshake</entry>
388
<entry>TLS handshake <emphasis>as TLS <quote>server</quote>
311
390
<entry><-><!-- ⟷ --></entry>
312
<entry>TLS handshake</entry>
391
<entry>TLS handshake <emphasis>as TLS <quote>client</quote>
315
<entry>OpenPGP public key (part of TLS handshake)</entry>
395
<entry>Public key (part of TLS handshake)</entry>
316
396
<entry>-><!-- → --></entry>
320
400
<entry><-<!-- ← --></entry>
321
<entry>Binary blob</entry>
401
<entry>Binary blob (client will assume OpenPGP data)</entry>
325
405
<entry><-<!-- ← --></entry>
326
406
<entry>Close</entry>
328
</tbody></tgroup></informaltable>
408
</tbody></tgroup></table>
411
<refsect1 id="checking">
412
<title>CHECKING</title>
414
The server will, by default, continually check that the clients
415
are still up. If a client has not been confirmed as being up
416
for some time, the client is assumed to be compromised and is no
417
longer eligible to receive the encrypted password. (Manual
418
intervention is required to re-enable a client.) The timeout,
419
extended timeout, checker program, and interval between checks
420
can be configured both globally and per client; see
421
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
422
<manvolnum>5</manvolnum></citerefentry>.
426
<refsect1 id="approval">
427
<title>APPROVAL</title>
429
The server can be configured to require manual approval for a
430
client before it is sent its secret. The delay to wait for such
431
approval and the default action (approve or deny) can be
432
configured both globally and per client; see <citerefentry>
433
<refentrytitle>mandos-clients.conf</refentrytitle>
434
<manvolnum>5</manvolnum></citerefentry>. By default all clients
435
will be approved immediately without delay.
438
This can be used to deny a client its secret if not manually
439
approved within a specified time. It can also be used to make
440
the server delay before giving a client its secret, allowing
441
optional manual denying of this specific client.
331
446
<refsect1 id="logging">
332
447
<title>LOGGING</title>
334
The server will log a lot of information with various severity
336
<citerefentry><refentrytitle>syslog</refentrytitle>
337
<manvolnum>8</manvolnum></citerefentry>. With the
449
The server will send log message with various severity levels to
450
<filename class="devicefile">/dev/log</filename>. With the
338
451
<option>--debug</option> option, it will log even more messages,
339
452
and also show them on the console.
456
<refsect1 id="persistent_state">
457
<title>PERSISTENT STATE</title>
459
Client settings, initially read from
460
<filename>clients.conf</filename>, are persistent across
461
restarts, and run-time changes will override settings in
462
<filename>clients.conf</filename>. However, if a setting is
463
<emphasis>changed</emphasis> (or a client added, or removed) in
464
<filename>clients.conf</filename>, this will take precedence.
468
<refsect1 id="dbus_interface">
469
<title>D-BUS INTERFACE</title>
471
The server will by default provide a D-Bus system bus interface.
472
This interface will only be accessible by the root user or a
473
Mandos-specific user, if such a user exists. For documentation
474
of the D-Bus API, see the file <filename>DBUS-API</filename>.
343
478
<refsect1 id="exit_status">
344
479
<title>EXIT STATUS</title>
347
482
critical error is encountered.
486
<refsect1 id="environment">
487
<title>ENVIRONMENT</title>
490
<term><envar>PATH</envar></term>
493
To start the configured checker (see <xref
494
linkend="checking"/>), the server uses
495
<filename>/bin/sh</filename>, which in turn uses
496
<varname>PATH</varname> to search for matching commands if
497
an absolute path is not given. See <citerefentry>
498
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
506
<refsect1 id="files">
352
507
<title>FILES</title>
356
<filename>/etc/mandos/mandos.conf</filename> See <citerefentry>
357
<refentrytitle>mandos.conf</refentrytitle>
358
<manvolnum>5</manvolnum></citerefentry>.
361
<filename>/etc/mandos/clients.conf</filename> See <citerefentry>
509
Use the <option>--configdir</option> option to change where
510
<command>&COMMANDNAME;</command> looks for its configurations
511
files. The default file names are listed here.
515
<term><filename>/etc/mandos/mandos.conf</filename></term>
518
Server-global settings. See
519
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
520
<manvolnum>5</manvolnum></citerefentry> for details.
525
<term><filename>/etc/mandos/clients.conf</filename></term>
528
List of clients and client-specific settings. See
529
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
530
<manvolnum>5</manvolnum></citerefentry> for details.
535
<term><filename>/run/mandos.pid</filename></term>
538
The file containing the process id of the
539
<command>&COMMANDNAME;</command> process started last.
540
<emphasis >Note:</emphasis> If the <filename
541
class="directory">/run</filename> directory does not
542
exist, <filename>/var/run/mandos.pid</filename> will be
549
class="directory">/var/lib/mandos</filename></term>
552
Directory where persistent state will be saved. Change
553
this with the <option>--statedir</option> option. See
554
also the <option>--no-restore</option> option.
559
<term><filename class="devicefile">/dev/log</filename></term>
562
The Unix domain socket to where local syslog messages are
568
<term><filename>/bin/sh</filename></term>
571
This is used to start the configured checker command for
572
each client. See <citerefentry>
362
573
<refentrytitle>mandos-clients.conf</refentrytitle>
363
<manvolnum>5</manvolnum></citerefentry>.
366
<filename>/var/run/mandos/mandos.pid</filename>
574
<manvolnum>5</manvolnum></citerefentry> for details.
372
581
<refsect1 id="bugs">
373
582
<title>BUGS</title>
584
This server might, on especially fatal errors, emit a Python
585
backtrace. This could be considered a feature.
378
<refsect1 id="examples">
379
<title>EXAMPLES</title>
588
There is no fine-grained control over logging and debug output.
590
<xi:include href="bugs.xml"/>
593
<refsect1 id="example">
594
<title>EXAMPLE</title>
597
Normal invocation needs no options:
600
<userinput>&COMMANDNAME;</userinput>
605
Run the server in debug mode, read configuration files from
606
the <filename class="directory">~/mandos</filename> directory,
607
and use the Zeroconf service name <quote>Test</quote> to not
608
collide with any other official Mandos server on this host:
612
<!-- do not wrap this line -->
613
<userinput>&COMMANDNAME; --debug --configdir ~/mandos --servicename Test</userinput>
619
Run the server normally, but only listen to one interface and
620
only on the link-local address on that interface:
624
<!-- do not wrap this line -->
625
<userinput>&COMMANDNAME; --interface eth7 --address fe80::aede:48ff:fe71:f6f2</userinput>
384
631
<refsect1 id="security">
385
632
<title>SECURITY</title>
633
<refsect2 id="server">
634
<title>SERVER</title>
636
Running this <command>&COMMANDNAME;</command> server program
637
should not in itself present any security risk to the host
638
computer running it. The program switches to a non-root user
642
<refsect2 id="clients">
643
<title>CLIENTS</title>
645
The server only gives out its stored data to clients which
646
does have the correct key ID of the stored key ID. This is
647
guaranteed by the fact that the client sends its public key in
648
the TLS handshake; this ensures it to be genuine. The server
649
computes the key ID of the key itself and looks up the key ID
650
in its list of clients. The <filename>clients.conf</filename>
652
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
653
<manvolnum>5</manvolnum></citerefentry>)
654
<emphasis>must</emphasis> be made non-readable by anyone
655
except the user starting the server (usually root).
658
As detailed in <xref linkend="checking"/>, the status of all
659
client computers will continually be checked and be assumed
660
compromised if they are gone for too long.
663
For more details on client-side security, see
664
<citerefentry><refentrytitle>mandos-client</refentrytitle>
665
<manvolnum>8mandos</manvolnum></citerefentry>.
390
670
<refsect1 id="see_also">
391
671
<title>SEE ALSO</title>
392
<itemizedlist spacing="compact">
394
<citerefentry><refentrytitle>password-request</refentrytitle>
395
<manvolnum>8mandos</manvolnum></citerefentry>
399
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
400
<manvolnum>8mandos</manvolnum></citerefentry>
404
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
408
<ulink url="http://www.avahi.org/">Avahi</ulink>
413
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
417
<citation>RFC 4880: <citetitle>OpenPGP Message
418
Format</citetitle></citation>
422
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
423
Transport Layer Security</citetitle></citation>
427
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
428
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
429
Unicast Addresses</citation>
673
<citerefentry><refentrytitle>intro</refentrytitle>
674
<manvolnum>8mandos</manvolnum></citerefentry>,
675
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
676
<manvolnum>5</manvolnum></citerefentry>,
677
<citerefentry><refentrytitle>mandos.conf</refentrytitle>
678
<manvolnum>5</manvolnum></citerefentry>,
679
<citerefentry><refentrytitle>mandos-client</refentrytitle>
680
<manvolnum>8mandos</manvolnum></citerefentry>,
681
<citerefentry><refentrytitle>sh</refentrytitle>
682
<manvolnum>1</manvolnum></citerefentry>
687
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
691
Zeroconf is the network protocol standard used by clients
692
for finding this Mandos server on the local network.
698
<ulink url="http://www.avahi.org/">Avahi</ulink>
702
Avahi is the library this server calls to implement
703
Zeroconf service announcements.
709
<ulink url="https://gnutls.org/">GnuTLS</ulink>
713
GnuTLS is the library this server uses to implement TLS for
714
communicating securely with the client, and at the same time
715
confidently get the client’s public key.
721
RFC 4291: <citetitle>IP Version 6 Addressing
722
Architecture</citetitle>
727
<term>Section 2.2: <citetitle>Text Representation of
728
Addresses</citetitle></term>
729
<listitem><para/></listitem>
732
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
733
Address</citetitle></term>
734
<listitem><para/></listitem>
737
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
738
Addresses</citetitle></term>
741
The clients use IPv6 link-local addresses, which are
742
immediately usable since a link-local addresses is
743
automatically assigned to a network interfaces when it
753
RFC 5246: <citetitle>The Transport Layer Security (TLS)
754
Protocol Version 1.2</citetitle>
758
TLS 1.2 is the protocol implemented by GnuTLS.
764
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
768
The data sent to clients is binary encrypted OpenPGP data.
774
RFC 7250: <citetitle>Using Raw Public Keys in Transport
775
Layer Security (TLS) and Datagram Transport Layer Security
780
This is implemented by GnuTLS version 3.6.6 and is, if
781
present, used by this server so that raw public keys can be
788
RFC 6091: <citetitle>Using OpenPGP Keys for Transport Layer
789
Security (TLS) Authentication</citetitle>
793
This is implemented by GnuTLS before version 3.6.0 and is,
794
if present, used by this server so that OpenPGP keys can be
802
<!-- Local Variables: -->
803
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
804
<!-- time-stamp-end: "[\"']>" -->
805
<!-- time-stamp-format: "%:y-%02m-%02d" -->