Module secret 

Passwords live in the system keyring, never in a file Sioul writes: the Secret Service on Linux (KWallet, GNOME Keyring), the Keychain on macOS, the Credential Manager on Windows (Cargo.toml chooses the backend per system). Each is filed under the service sioul and <login> on <server>, so it is easy to find, check or remove there.

Constants

SERVICE 🔒

Functions

entry 🔒

forget

Forgets the account’s password; nothing to do if there was none.

forget_named

Forgets a secret kept under a name of Sioul’s; nothing to do if there was none.

named

A secret kept under a name of Sioul’s (“Bitwarden device token for …”).

passphrase_entry 🔒

password

The password kept for the account. A mail account signed in with Google has none: what stands for it is its grant’s mark (sasl::OAuth::mark), unused by the servers, which are given an access token instead; no grant kept here, Google’s sign-in is asked again.

pgp_passphrase

The passphrase of your OpenPGP key, when the keyring keeps it.

save

Keeps the password for the account, replacing any older one.

save_named

Keeps a secret under a name of Sioul’s.

save_pgp_passphrase

Keeps the passphrase of your OpenPGP key in the keyring.

test_passphrase

In a test build with SIOUL_TEST_PASSWORD, the passphrase every key gets (the keyring is left alone); None in Sioul’s builds.

testing 🔒

Tests against a local server leave the keyring alone (never in Sioul’s builds).