| 1 | Source: distorted-keys |
| 2 | Section: utils |
| 3 | Priority: optional |
| 4 | Maintainer: Mark Wooding <mdw@distorted.org.uk> |
| 5 | Build-Depends: python (>= 2.5), debhelper (>= 8.1.2) |
| 6 | Standards-Version: 3.1.1 |
| 7 | |
| 8 | Package: distorted-keys |
| 9 | Architecture: all |
| 10 | Depends: python (>= 2.5), userv, openssl (>= 0.9.8o), adduser |
| 11 | Recommends: gnupg |
| 12 | Suggests: seccure, texlive-latex-recommended, qrencode |
| 13 | Description: Basic key-management system with secure recovery features. |
| 14 | The primary purpose of the distorted.org.uk key management system is |
| 15 | to provide a secure way of recovering important cryptographic keys, |
| 16 | e.g., keys for decrypting backup volumes, in the event of a disaster. |
| 17 | . |
| 18 | Because it was technically fairly easy, given this infrastructure, the |
| 19 | system also allows users to generate and use their own keys, without |
| 20 | revealing the actual key data, on the theory that, what a user program |
| 21 | doesn't know, it can't leak. |
| 22 | . |
| 23 | This system doesn't actually do very much cryptography itself. Instead, |
| 24 | it uses other existing implementations, such as GnuPG, OpenSSL, and |
| 25 | Seccure. |