Available on Linux only.
Expand description
§Linux (keyutils) store with Secret Service backing
This store, contributed by @soywod, uses the keyutils module as a cache available to headless processes, while using the secret-service module to provide credential storage beyond reboot. The expected usage pattern for this module is as follows:
- Processes that run on headless systems are built with
keyutilssupport via thelinux-nativefeature of this crate. After each reboot, these processes are either launched after the keyutils cache has been reloaded from the secret service, or (if launched immediately) they wait until the keyutils cache has been reloaded. - A headed “configuration” process is built with this module that allows its user to configure the credentials needed by the headless processes. After each reboot, this process unlocks the secret service (see both the keyutils and secret-service module for information about how this can be done headlessly, if desired) and then accesses each of the configured credentials (which loads them into keyutils). At that point the headless clients can be started (or become active, if already started).
This store works by creating a keyutils entry and a secret-service entry for each of its entries. Because keyutils entries don’t have attributes, entries in this store don’t expose attributes either. Because keyutils entries can’t store empty passwords/secrets, this store’s entries can’t either.
See the documentation for the keyutils and secret-service modules if you
want details about how the underlying storage is handled.
Structs§
- Keyutils
Persistent Credential - Representation of a keyutils-persistent credential.
- Keyutils
Persistent Credential Builder - The builder for keyutils-persistent credentials
Functions§
- default_
credential_ builder - Returns an instance of the keyutils-persistent credential builder.