/mandos/release

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/release

« back to all changes in this revision

Viewing changes to intro.xml

  • Committer: Teddy Hogeborn
  • Date: 2019-02-10 03:50:20 UTC
  • mto: (237.7.594 trunk)
  • mto: This revision was merged to the branch mainline in revision 370.
  • Revision ID: teddy@recompile.se-20190210035020-nttr1tybgwwixueu
http://bugs.debian.org/879538
http://bugs.debian.org/916673
Show debconf note about new TLS key IDs

If mandos-client did not see TLS keys and had to create them, or if
mandos sees GnuTLS version 3.6.6 or later, show an important notice on
package installation about the importance of adding the new key_id
options to clients.conf on the Mandos server.

* debian/control (Package: mandos, Package: mandos-client): Depend on
                                                            debconf.
* debian/mandos-client.lintian-overrides: Override warnings.
* debian/mandos-client.postinst (create_keys): Show notice if new TLS
                                               key files were created.
* debian/mandos-client.templates: New.
* debian/mandos.lintian-overrides: Override warnings.
* debian/mandos.postinst (configure): If GnuTLS 3.6.6 or later is
                                      detected, show an important
                                      notice (once) about the new
                                      key_id option required in
                                      clients.conf.
* debian/mandos.templates: New.

Show diffs side-by-side

added added

removed removed

Lines of Context:
intro.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 TIMESTAMP "2017-02-23">
 
4
<!ENTITY TIMESTAMP "2019-02-09">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
37
37
      <year>2015</year>
38
38
      <year>2016</year>
39
39
      <year>2017</year>
 
40
      <year>2018</year>
40
41
      <holder>Teddy Hogeborn</holder>
41
42
      <holder>Björn Påhlsson</holder>
42
43
    </copyright>
66
67
      The computers run a small client program in the initial RAM disk
67
68
      environment which will communicate with a server over a network.
68
69
      All network communication is encrypted using TLS.  The clients
69
 
      are identified by the server using an OpenPGP key; each client
 
70
      are identified by the server using a TLS public key; each client
70
71
      has one unique to it.  The server sends the clients an encrypted
71
72
      password.  The encrypted password is decrypted by the clients
72
 
      using the same OpenPGP key, and the password is then used to
 
73
      using a separate OpenPGP key, and the password is then used to
73
74
      unlock the root file system, whereupon the computers can
74
75
      continue booting normally.
75
76
    </para>
199
200
      <para>
200
201
        No.  The server only gives out the passwords to clients which
201
202
        have <emphasis>in the TLS handshake</emphasis> proven that
202
 
        they do indeed hold the OpenPGP private key corresponding to
203
 
        that client.
 
203
        they do indeed hold the private key corresponding to that
 
204
        client.
204
205
      </para>
205
206
    </refsect2>
206
207