~mdw / udpkey / blame
| Commit | Line | Data |
|---|---|---|
| 247f344a MW |
1 | Source: udpkey |
| 2 | Section: utils | |
| 3 | Priority: extra | |
| 4 | Maintainer: Mark Wooding <mdw@distorted.org.uk> | |
| 5c7e9df8 MW |
5 | Build-Depends: debhelper (>= 8), pkg-config, |
| 6 | mlib-dev (>= 2.2.1~pre), catacomb-dev (>= 2.1.4) | |
| 247f344a MW |
7 | Standards-Version: 3.1.1 |
| 8 | ||
| 9 | Package: udpkey | |
| 10 | Architecture: any | |
| 11 | Depends: ${shlibs:Depends} | |
| 12 | Recommends: catacomb-bin | |
| 13 | Suggests: cryptsetup | |
| 14 | Description: Fetch or serve cryptographic keys over a network. | |
| 15 | The udpkey program can fetch key data from remote servers using a simple | |
| 16 | UDP-baed cryptographic protocol; or can can run as a server, providing key | |
| 17 | material on request to authorized clients. | |
| 18 | . | |
| 19 | When running as a client, the program fetches key fragments from multiple | |
| 20 | sources, combining them together. It can read key fragments from local | |
| 21 | files or request them from servers. Key data can be split among many | |
| 22 | servers for increased security, and individual fragments can be held on and | |
| 23 | requested from multiple servers for increased availability. | |
| 24 | . | |
| 25 | The client can be run in early userland, e.g., in initramfs, to obtain key | |
| 26 | material for decrypting a server's disks. | |
| 27 | . | |
| 28 | When running as a server, the program responds to requests, verifying that | |
| 29 | the client is authorized, and encrypting the requested key fragment with the | |
| 30 | appropriate client-specific public key. |