/mandos/trunk

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/trunk
185 by Teddy Hogeborn
* .bzr-builddeb/default.conf: New.
1
Source: mandos
2
Section: admin
3
Priority: extra
4
Maintainer: Mandos Maintainers <mandos@fukt.bsnet.se>
5
Build-Depends: debhelper (>= 7), docbook-xsl, docbook (<5.0),
6
	libavahi-core-dev, libgpgme11-dev, libgnutls-dev, xsltproc
7
Standards-Version: 3.8.0
8
Vcs-Bzr: ftp://anonymous@ftp.fukt.bsnet.se/pub/mandos/latest
9
Homepage: http://www.fukt.bsnet.se/mandos
10
11
Package: mandos
12
Architecture: all
13
Depends: ${shlibs:Depends}, ${misc:Depends}, python (>=2.5),
14
	python-gnutls, python-dbus, python-avahi, avahi-daemon,
15
	gnupg (< 2)
16
Recommends: fping
17
Description: a server giving encrypted passwords to Mandos clients
18
 This is the server part of the Mandos system, which allows
19
 computers to have encrypted root file systems and at the
20
 same time be capable of remote and/or unattended reboots.
21
 .
22
 The computers run a small client program in the initial RAM
23
 disk environment which will communicate with a server over a
24
 network.  All network communication is encrypted using TLS.
25
 The clients are identified by the server using an OpenPGP
26
 key; each client has one unique to it.  The server sends the
27
 clients an encrypted password.  The encrypted password is
28
 decrypted by the clients using the same OpenPGP key, and the
29
 password is then used to unlock the root file system,
30
 whereupon the computers can continue booting normally.
31
32
Package: mandos-client
33
Architecture: any
34
Depends: ${shlibs:Depends}, ${misc:Depends}
35
Enhances: cryptsetup
36
Description: do unattended reboots with an encrypted root file system
37
 This is the client part of the Mandos system, which allows
38
 computers to have encrypted root file systems and at the
39
 same time be capable of remote and/or unattended reboots.
40
 .
41
 The computers run a small client program in the initial RAM
42
 disk environment which will communicate with a server over a
43
 network.  All network communication is encrypted using TLS.
44
 The clients are identified by the server using an OpenPGP
45
 key; each client has one unique to it.  The server sends the
46
 clients an encrypted password.  The encrypted password is
47
 decrypted by the clients using the same OpenPGP key, and the
48
 password is then used to unlock the root file system,
49
 whereupon the computers can continue booting normally.