sequoia-keystore-server
| Crates.io | sequoia-keystore-server |
| lib.rs | sequoia-keystore-server |
| version | 0.1.0 |
| source | src |
| created_at | 2024-08-31 12:58:54.213667 |
| updated_at | 2024-08-31 12:58:54.213667 |
| description | Sequoia keystore daemon |
| homepage | https://sequoia-pgp.org/ |
| repository | https://gitlab.com/sequoia-pgp/sequoia-keystore |
| max_upload_size | |
| id | 1358812 |
| size | 86,332 |
Justus Winter (teythoon)
documentation
README
Sequoia's keystore server.
This program is a simple wrapper around the [sequoia-keystore]
library, which runs as a server. Normally programs like sq will
automatically start servers on demand (by default they look for the
executables in /usr/local/lib/sequoia). This crate's binary,
sequoia-keystore, should be installed in /usr/local/lib/sequoia so
that sq and other programs can find it.
Servers can also be started explicitly by just running the binary.
If the server can't be started, the server is also usually embedded in the programs, and an in-process server is used instead. The in-process server has several disadvantages, though:
-
Secret key material is in the same process, which makes the program more vulnerable to Heartbleed-style attacks.
-
It may be harder to use resources like smart cards from multiple process.
-
Passwords will only be cached locally.
In some cases, the in-process server is preferable, like early in the boot process when starting processes is hard, or the file system is not completely setup.