To get this branch, use:
bzr branch
http://bzr.recompile.se/loggerhead/mandos/release
« back to all changes in this revision
Viewing changes to mandos.xml
- browse files at revision 124
- compare with another revision
- download diff
- download tarball
- view history from revision 124
- Committer: Teddy Hogeborn
- Date: 2008-08-31 09:26:12 UTC
- Revision ID: teddy@fukt.bsnet.se-20080831092612-atz9uzia38h1ijy5
* mandos.xml (OPTIONS): Moved long options before short. Use <option>
tags instead of <literal>.
tags instead of <literal>.
- files added:
- initramfs-tools-hook-conf
- files removed:
- .bzr-builddeb
- debian
- debian/po
- debian/source
- debian/tests
- debian/upstream
- dracut-module
- network-hooks.d
- plugin-helpers
- files renamed:
- plugins.d/mandos-client.c => plugins.d/password-request.c
- plugins.d/mandos-client.xml => plugins.d/password-request.xml
- files modified:
- .bzrignore
added
removed
mandos.xml
1
1
<?xml version="1.0" encoding="UTF-8"?>
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
<!ENTITY VERSION "1.0">
4
5
<!ENTITY COMMANDNAME "mandos">
5
<!ENTITY TIMESTAMP "2019-07-24">
6
<!ENTITY % common SYSTEM "common.ent">
7
%common;
6
<!ENTITY TIMESTAMP "2008-08-31">
8
7
]>
9
8
10
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
11
<refentryinfo>
10
<refentryinfo>
12
11
<title>Mandos Manual</title>
13
12
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
13
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
14
<productnumber>&VERSION;</productnumber>
16
15
<date>&TIMESTAMP;</date>
17
16
<authorgroup>
18
17
<author>
19
18
<firstname>Björn</firstname>
20
19
<surname>Påhlsson</surname>
21
20
<address>
22
<email>belorn@recompile.se</email>
21
<email>belorn@fukt.bsnet.se</email>
23
22
</address>
24
23
</author>
25
24
<author>
26
25
<firstname>Teddy</firstname>
27
26
<surname>Hogeborn</surname>
28
27
<address>
29
<email>teddy@recompile.se</email>
28
<email>teddy@fukt.bsnet.se</email>
30
29
</address>
31
30
</author>
32
31
</authorgroup>
33
32
<copyright>
34
33
<year>2008</year>
35
<year>2009</year>
36
<year>2010</year>
37
<year>2011</year>
38
<year>2012</year>
39
<year>2013</year>
40
<year>2014</year>
41
<year>2015</year>
42
<year>2016</year>
43
<year>2017</year>
44
<year>2018</year>
45
<year>2019</year>
46
34
<holder>Teddy Hogeborn</holder>
47
35
<holder>Björn Påhlsson</holder>
48
36
</copyright>
49
<xi:include href="legalnotice.xml"/>
37
<legalnotice>
38
<para>
39
This manual page is free software: you can redistribute it
40
and/or modify it under the terms of the GNU General Public
41
License as published by the Free Software Foundation,
42
either version 3 of the License, or (at your option) any
43
later version.
44
</para>
45
46
<para>
47
This manual page is distributed in the hope that it will
48
be useful, but WITHOUT ANY WARRANTY; without even the
49
implied warranty of MERCHANTABILITY or FITNESS FOR A
50
PARTICULAR PURPOSE. See the GNU General Public License
51
for more details.
52
</para>
53
54
<para>
55
You should have received a copy of the GNU General Public
56
License along with this program; If not, see
57
<ulink url="http://www.gnu.org/licenses/"/>.
58
</para>
59
</legalnotice>
50
60
</refentryinfo>
51
61
52
62
<refmeta>
53
63
<refentrytitle>&COMMANDNAME;</refentrytitle>
54
64
<manvolnum>8</manvolnum>
60
70
Gives encrypted passwords to authenticated Mandos clients
61
71
</refpurpose>
62
72
</refnamediv>
63
73
64
74
<refsynopsisdiv>
65
75
<cmdsynopsis>
66
76
<command>&COMMANDNAME;</command>
95
105
<replaceable>DIRECTORY</replaceable></option></arg>
96
106
<sbr/>
97
107
<arg><option>--debug</option></arg>
98
<sbr/>
99
<arg><option>--debuglevel
100
<replaceable>LEVEL</replaceable></option></arg>
101
<sbr/>
102
<arg><option>--no-dbus</option></arg>
103
<sbr/>
104
<arg><option>--no-ipv6</option></arg>
105
<sbr/>
106
<arg><option>--no-restore</option></arg>
107
<sbr/>
108
<arg><option>--statedir
109
<replaceable>DIRECTORY</replaceable></option></arg>
110
<sbr/>
111
<arg><option>--socket
112
<replaceable>FD</replaceable></option></arg>
113
<sbr/>
114
<arg><option>--foreground</option></arg>
115
<sbr/>
116
<arg><option>--no-zeroconf</option></arg>
117
108
</cmdsynopsis>
118
109
<cmdsynopsis>
119
110
<command>&COMMANDNAME;</command>
131
122
<arg choice="plain"><option>--check</option></arg>
132
123
</cmdsynopsis>
133
124
</refsynopsisdiv>
134
125
135
126
<refsect1 id="description">
136
127
<title>DESCRIPTION</title>
137
128
<para>
138
129
<command>&COMMANDNAME;</command> is a server daemon which
139
130
handles incoming request for passwords for a pre-defined list of
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.
131
client host computers. The Mandos server uses Zeroconf to
132
announce itself on the local network, and uses TLS to
133
communicate securely with and to authenticate the clients. The
134
Mandos server uses IPv6 to allow Mandos clients to use IPv6
135
link-local addresses, since the clients will probably not have
136
any other addresses configured (see <xref linkend="overview"/>).
137
Any authenticated client is then given the stored pre-encrypted
138
password for that specific client.
150
139
</para>
140
151
141
</refsect1>
152
142
153
143
<refsect1 id="purpose">
154
144
<title>PURPOSE</title>
145
155
146
<para>
156
147
The purpose of this is to enable <emphasis>remote and unattended
157
148
rebooting</emphasis> of client host computer with an
158
149
<emphasis>encrypted root file system</emphasis>. See <xref
159
150
linkend="overview"/> for details.
160
151
</para>
152
161
153
</refsect1>
162
154
163
155
<refsect1 id="options">
164
156
<title>OPTIONS</title>
157
165
158
<variablelist>
166
159
<varlistentry>
167
160
<term><option>--help</option></term>
219
212
<xi:include href="mandos-options.xml" xpointer="debug"/>
220
213
</listitem>
221
214
</varlistentry>
222
223
<varlistentry>
224
<term><option>--debuglevel
225
<replaceable>LEVEL</replaceable></option></term>
226
<listitem>
227
<para>
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>.
237
</para>
238
</listitem>
239
</varlistentry>
240
215
241
216
<varlistentry>
242
217
<term><option>--priority <replaceable>
243
218
PRIORITY</replaceable></option></term>
245
220
<xi:include href="mandos-options.xml" xpointer="priority"/>
246
221
</listitem>
247
222
</varlistentry>
248
223
249
224
<varlistentry>
250
225
<term><option>--servicename
251
226
<replaceable>NAME</replaceable></option></term>
254
229
xpointer="servicename"/>
255
230
</listitem>
256
231
</varlistentry>
257
232
258
233
<varlistentry>
259
234
<term><option>--configdir
260
235
<replaceable>DIRECTORY</replaceable></option></term>
269
244
</para>
270
245
</listitem>
271
246
</varlistentry>
272
247
273
248
<varlistentry>
274
249
<term><option>--version</option></term>
275
250
<listitem>
278
253
</para>
279
254
</listitem>
280
255
</varlistentry>
281
282
<varlistentry>
283
<term><option>--no-dbus</option></term>
284
<listitem>
285
<xi:include href="mandos-options.xml" xpointer="dbus"/>
286
<para>
287
See also <xref linkend="dbus_interface"/>.
288
</para>
289
</listitem>
290
</varlistentry>
291
292
<varlistentry>
293
<term><option>--no-ipv6</option></term>
294
<listitem>
295
<xi:include href="mandos-options.xml" xpointer="ipv6"/>
296
</listitem>
297
</varlistentry>
298
299
<varlistentry>
300
<term><option>--no-restore</option></term>
301
<listitem>
302
<xi:include href="mandos-options.xml" xpointer="restore"/>
303
<para>
304
See also <xref linkend="persistent_state"/>.
305
</para>
306
</listitem>
307
</varlistentry>
308
309
<varlistentry>
310
<term><option>--statedir
311
<replaceable>DIRECTORY</replaceable></option></term>
312
<listitem>
313
<xi:include href="mandos-options.xml" xpointer="statedir"/>
314
</listitem>
315
</varlistentry>
316
317
<varlistentry>
318
<term><option>--socket
319
<replaceable>FD</replaceable></option></term>
320
<listitem>
321
<xi:include href="mandos-options.xml" xpointer="socket"/>
322
</listitem>
323
</varlistentry>
324
325
<varlistentry>
326
<term><option>--foreground</option></term>
327
<listitem>
328
<xi:include href="mandos-options.xml"
329
xpointer="foreground"/>
330
</listitem>
331
</varlistentry>
332
333
<varlistentry>
334
<term><option>--no-zeroconf</option></term>
335
<listitem>
336
<xi:include href="mandos-options.xml" xpointer="zeroconf"/>
337
</listitem>
338
</varlistentry>
339
340
256
</variablelist>
341
257
</refsect1>
342
258
343
259
<refsect1 id="overview">
344
260
<title>OVERVIEW</title>
345
261
<xi:include href="overview.xml"/>
346
262
<para>
347
263
This program is the server part. It is a normal server program
348
264
and will run in a normal system environment, not in an initial
349
<acronym>RAM</acronym> disk environment.
265
RAM disk environment.
350
266
</para>
351
267
</refsect1>
352
268
353
269
<refsect1 id="protocol">
354
270
<title>NETWORK PROTOCOL</title>
355
271
<para>
362
278
start a TLS protocol handshake with a slight quirk: the Mandos
363
279
server program acts as a TLS <quote>client</quote> while the
364
280
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.
281
The Mandos client must supply an OpenPGP certificate, and the
282
fingerprint of this certificate is used by the Mandos server to
283
look up (in a list read from <filename>clients.conf</filename>
284
at start time) which binary blob to give the client. No other
285
authentication or authorization is done by the server.
370
286
</para>
371
287
<table>
372
288
<title>Mandos Protocol (Version 1)</title><tgroup cols="3"><thead>
392
308
</emphasis></entry>
393
309
</row>
394
310
<row>
395
<entry>Public key (part of TLS handshake)</entry>
311
<entry>OpenPGP public key (part of TLS handshake)</entry>
396
312
<entry>-><!-- → --></entry>
397
313
</row>
398
314
<row>
407
323
</row>
408
324
</tbody></tgroup></table>
409
325
</refsect1>
410
326
411
327
<refsect1 id="checking">
412
328
<title>CHECKING</title>
413
329
<para>
414
330
The server will, by default, continually check that the clients
415
331
are still up. If a client has not been confirmed as being up
416
332
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>
333
longer eligible to receive the encrypted password. The timeout,
334
checker program, and interval between checks can be configured
335
both globally and per client; see <citerefentry>
336
<refentrytitle>mandos-clients.conf</refentrytitle>
422
337
<manvolnum>5</manvolnum></citerefentry>.
423
338
</para>
424
339
</refsect1>
425
426
<refsect1 id="approval">
427
<title>APPROVAL</title>
428
<para>
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.
436
</para>
437
<para>
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.
442
</para>
443
444
</refsect1>
445
340
446
341
<refsect1 id="logging">
447
342
<title>LOGGING</title>
448
343
<para>
449
344
The server will send log message with various severity levels to
450
<filename class="devicefile">/dev/log</filename>. With the
345
<filename>/dev/log</filename>. With the
451
346
<option>--debug</option> option, it will log even more messages,
452
347
and also show them on the console.
453
348
</para>
454
349
</refsect1>
455
456
<refsect1 id="persistent_state">
457
<title>PERSISTENT STATE</title>
458
<para>
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.
465
</para>
466
</refsect1>
467
468
<refsect1 id="dbus_interface">
469
<title>D-BUS INTERFACE</title>
470
<para>
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>.
475
</para>
476
</refsect1>
477
350
478
351
<refsect1 id="exit_status">
479
352
<title>EXIT STATUS</title>
480
353
<para>
482
355
critical error is encountered.
483
356
</para>
484
357
</refsect1>
485
358
486
359
<refsect1 id="environment">
487
360
<title>ENVIRONMENT</title>
488
361
<variablelist>
502
375
</varlistentry>
503
376
</variablelist>
504
377
</refsect1>
505
506
<refsect1 id="files">
378
379
<refsect1 id="file">
507
380
<title>FILES</title>
508
381
<para>
509
382
Use the <option>--configdir</option> option to change where
532
405
</listitem>
533
406
</varlistentry>
534
407
<varlistentry>
535
<term><filename>/run/mandos.pid</filename></term>
536
<listitem>
537
<para>
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
543
used instead.
544
</para>
545
</listitem>
546
</varlistentry>
547
<varlistentry>
548
<term><filename
549
class="directory">/var/lib/mandos</filename></term>
550
<listitem>
551
<para>
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.
555
</para>
556
</listitem>
557
</varlistentry>
558
<varlistentry>
559
<term><filename class="devicefile">/dev/log</filename></term>
408
<term><filename>/var/run/mandos/mandos.pid</filename></term>
409
<listitem>
410
<para>
411
The file containing the process id of
412
<command>&COMMANDNAME;</command>.
413
</para>
414
</listitem>
415
</varlistentry>
416
<varlistentry>
417
<term><filename>/dev/log</filename></term>
560
418
<listitem>
561
419
<para>
562
420
The Unix domain socket to where local syslog messages are
585
443
backtrace. This could be considered a feature.
586
444
</para>
587
445
<para>
446
Currently, if a client is declared <quote>invalid</quote> due to
447
having timed out, the server does not record this fact onto
448
permanent storage. This has some security implications, see
449
<xref linkend="CLIENTS"/>.
450
</para>
451
<para>
452
There is currently no way of querying the server of the current
453
status of clients, other than analyzing its <systemitem
454
class="service">syslog</systemitem> output.
455
</para>
456
<para>
588
457
There is no fine-grained control over logging and debug output.
589
458
</para>
590
<xi:include href="bugs.xml"/>
459
<para>
460
Debug mode is conflated with running in the foreground.
461
</para>
462
<para>
463
The console log messages does not show a timestamp.
464
</para>
591
465
</refsect1>
592
466
593
467
<refsect1 id="example">
603
477
<informalexample>
604
478
<para>
605
479
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:
480
the <filename>~/mandos</filename> directory, and use the
481
Zeroconf service name <quote>Test</quote> to not collide with
482
any other official Mandos server on this host:
609
483
</para>
610
484
<para>
611
485
627
501
</para>
628
502
</informalexample>
629
503
</refsect1>
630
504
631
505
<refsect1 id="security">
632
506
<title>SECURITY</title>
633
<refsect2 id="server">
507
<refsect2 id="SERVER">
634
508
<title>SERVER</title>
635
509
<para>
636
510
Running this <command>&COMMANDNAME;</command> server program
637
511
should not in itself present any security risk to the host
638
computer running it. The program switches to a non-root user
639
soon after startup.
512
computer running it. The program does not need any special
513
privileges to run, and is designed to run as a non-root user.
640
514
</para>
641
515
</refsect2>
642
<refsect2 id="clients">
516
<refsect2 id="CLIENTS">
643
517
<title>CLIENTS</title>
644
518
<para>
645
519
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>
651
file (see
520
does have the OpenPGP key of the stored fingerprint. This is
521
guaranteed by the fact that the client sends its OpenPGP
522
public key in the TLS handshake; this ensures it to be
523
genuine. The server computes the fingerprint of the key
524
itself and looks up the fingerprint in its list of
525
clients. The <filename>clients.conf</filename> file (see
652
526
<citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
653
527
<manvolnum>5</manvolnum></citerefentry>)
654
528
<emphasis>must</emphasis> be made non-readable by anyone
655
except the user starting the server (usually root).
529
except the user running the server.
656
530
</para>
657
531
<para>
658
532
As detailed in <xref linkend="checking"/>, the status of all
660
534
compromised if they are gone for too long.
661
535
</para>
662
536
<para>
537
If a client is compromised, its downtime should be duly noted
538
by the server which would therefore declare the client
539
invalid. But if the server was ever restarted, it would
540
re-read its client list from its configuration file and again
541
regard all clients therein as valid, and hence eligible to
542
receive their passwords. Therefore, be careful when
543
restarting servers if it is suspected that a client has, in
544
fact, been compromised by parties who may now be running a
545
fake Mandos client with the keys from the non-encrypted
546
initial RAM image of the client host. What should be done in
547
that case (if restarting the server program really is
548
necessary) is to stop the server program, edit the
549
configuration file to omit any suspect clients, and restart
550
the server program.
551
</para>
552
<para>
663
553
For more details on client-side security, see
664
<citerefentry><refentrytitle>mandos-client</refentrytitle>
554
<citerefentry><refentrytitle>password-request</refentrytitle>
665
555
<manvolnum>8mandos</manvolnum></citerefentry>.
666
556
</para>
667
557
</refsect2>
668
558
</refsect1>
669
559
670
560
<refsect1 id="see_also">
671
561
<title>SEE ALSO</title>
672
562
<para>
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>
563
<citerefentry>
564
<refentrytitle>mandos-clients.conf</refentrytitle>
565
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
566
<refentrytitle>mandos.conf</refentrytitle>
567
<manvolnum>5</manvolnum></citerefentry>, <citerefentry>
568
<refentrytitle>password-request</refentrytitle>
569
<manvolnum>8mandos</manvolnum></citerefentry>, <citerefentry>
570
<refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum>
571
</citerefentry>
683
572
</para>
684
573
<variablelist>
685
574
<varlistentry>
695
584
</varlistentry>
696
585
<varlistentry>
697
586
<term>
698
<ulink url="https://www.avahi.org/">Avahi</ulink>
587
<ulink url="http://www.avahi.org/">Avahi</ulink>
699
588
</term>
700
589
<listitem>
701
590
<para>
706
595
</varlistentry>
707
596
<varlistentry>
708
597
<term>
709
<ulink url="https://gnutls.org/">GnuTLS</ulink>
598
<ulink url="http://www.gnu.org/software/gnutls/"
599
>GnuTLS</ulink>
710
600
</term>
711
601
<listitem>
712
602
<para>
713
603
GnuTLS is the library this server uses to implement TLS for
714
604
communicating securely with the client, and at the same time
715
confidently get the client’s public key.
605
confidently get the client’s public OpenPGP key.
716
606
</para>
717
607
</listitem>
718
608
</varlistentry>
750
640
</varlistentry>
751
641
<varlistentry>
752
642
<term>
753
RFC 5246: <citetitle>The Transport Layer Security (TLS)
754
Protocol Version 1.2</citetitle>
643
RFC 4346: <citetitle>The Transport Layer Security (TLS)
644
Protocol Version 1.1</citetitle>
755
645
</term>
756
646
<listitem>
757
647
<para>
758
TLS 1.2 is the protocol implemented by GnuTLS.
648
TLS 1.1 is the protocol implemented by GnuTLS.
759
649
</para>
760
650
</listitem>
761
651
</varlistentry>
771
661
</varlistentry>
772
662
<varlistentry>
773
663
<term>
774
RFC 7250: <citetitle>Using Raw Public Keys in Transport
775
Layer Security (TLS) and Datagram Transport Layer Security
776
(DTLS)</citetitle>
777
</term>
778
<listitem>
779
<para>
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
782
used.
783
</para>
784
</listitem>
785
</varlistentry>
786
<varlistentry>
787
<term>
788
RFC 6091: <citetitle>Using OpenPGP Keys for Transport Layer
789
Security (TLS) Authentication</citetitle>
790
</term>
791
<listitem>
792
<para>
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
795
used.
664
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
665
Security</citetitle>
666
</term>
667
<listitem>
668
<para>
669
This is implemented by GnuTLS and used by this server so
670
that OpenPGP keys can be used.
796
671
</para>
797
672
</listitem>
798
673
</varlistentry>
Loggerhead is a web-based interface for Breezy
Version: 2.0.2.dev0