/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 overview.xml

  • Committer: Teddy Hogeborn
  • Date: 2019-02-11 06:14:29 UTC
  • mto: (237.7.594 trunk)
  • mto: This revision was merged to the branch mainline in revision 376.
  • Revision ID: teddy@recompile.se-20190211061429-n6n5zk29iatshlb3
Fix Debian package dependencies

* debian/control (Build-Depends): Changed GnuTLS dependencies to
                                  "libgnutls30 (>= 3.3.0),
                                  libgnutls28-dev (>= 3.6.6) |
                                  libgnutls28-dev (<< 3.6.0)".  (We
                                  can't depend on the virtual package
                                  "gnutls-dev", since we need the
                                  version restrictions.)
  (Package: mandos/Depends): Remove dependency on libgnutls28-dev
                             package.
  (Package: mandos/Suggests): New; set to "libc6-dev,
                              c-compiler". (Used to find value of
                              "SO_BINDTODEVICE").
  (Package: mandos-client/Depends): Don't depend on openssl anymore;
                                    instead depend on either a
                                    gnutls-bin (>= 3.6.6) (in which
                                    case TLS key generation will
                                    work), or on libgnutls30 (<<
                                    3.6.0) (in which case TLS key
                                    generation will not be needed).

Show diffs side-by-side

added added

removed removed

Lines of Context:
overview.xml
6
6
  encrypted root file systems and at the same time be capable of
7
7
  remote and/or unattended reboots.  The computers run a small client
8
8
  program in the initial <acronym>RAM</acronym> disk environment which
9
 
  will communicate with a server over a network.  The clients are
10
 
  identified by the server using a OpenPGP key; each client has one
11
 
  unique to it.  The server sends the clients an encrypted password.
12
 
  The encrypted password is decrypted by the clients using the same
13
 
  OpenPGP key, and the password is then used to unlock the root file
14
 
  system, whereupon the computers can continue booting normally.
 
9
  will communicate with a server over a network.  All network
 
10
  communication is encrypted using <acronym>TLS</acronym>.  The
 
11
  clients are identified by the server using a TLS key; each client
 
12
  has one unique to it.  The server sends the clients an encrypted
 
13
  password.  The encrypted password is decrypted by the clients using
 
14
  a separate OpenPGP key, and the password is then used to unlock the
 
15
  root file system, whereupon the computers can continue booting
 
16
  normally.
15
17
</para>