KDE Wallet Manager is a tool to manage passwords on the KDE Plasma system. By using the KWallet subsystem it not only allows you to keep your own secrets but also to access and manage the passwords of every application that integrates with KWallet.
Unlock KDE Wallet automatically on login
- GnuPG keys, the KDE Wallet must use the standard
is not compatible with
- The chosen KWallet password must be the same as the current user password.
- The wallet cannot be unlocked when using autologin.
- The wallet cannot be unlocked when using a fingerprint reader to login
- The wallet must be named
kdewallet(default name). It does not unlock any other wallet(s).
- If using KDE, one may want to disable Close when last application stops using it in KDE Wallet settings to prevent the wallet from being closed after each usage (WiFi-passphrase unlock, etc.).
- It may be needed to remove the default created wallet first, thus removing all stored entries.
- If the kwallet Migration Assistant asks for a password after every login, rename or delete the
Optional install for the wallet management tool. This tool can be used to create a KDE Wallet with
blowfish encryption and more settings not provided by the kcm-module.
The following lines must be present under their corresponding sections:
auth optional pam_kwallet5.so session optional pam_kwallet5.so auto_start
Edit the PAM configuration corresponding to your situation:
- For SDDM no further edits should be needed because the lines are already present in
- For GDM edit
- For LightDM edit
- For unlocking on tty login (no display manager), edit
#%PAM-1.0 auth include system-login auth optional pam_kwallet5.so account include system-login password include system-login session include system-login session optional pam_kwallet5.so auto_start
Using the KDE Wallet to store ssh key passphrases
#!/bin/sh ssh-add -q < /dev/null
~/.ssh/id_rsa. Assuming you have different SSH keys named
~/.ssh/, you may add them automatically on login by changing the above script to:
#!/bin/sh ssh-add -q ~/.ssh/key1 ~/.ssh/key2 ~/.ssh/key3 < /dev/null
#!/bin/sh export SSH_ASKPASS='/usr/bin/ksshaskpass'
It will ask for your password and unlock your SSH keys. Upon restart your SSH keys should be unlocked once you give your kwallet password.
To add a new key and store the password with kwallet use the following command
$ ssh-add /path/to/new/key </dev/null
and append the key to the list of keys in
~/.config/autostart-scripts/ssh-add.sh as explained above to have it unlocked upon providing the kwallet password.
Using the KDE Wallet to store Git credentials
Git can delegate credential handling to a credential helper. By using as a credential helper, the HTTP/HTTPS and SMTP passwords can be safely stored in the KDE Wallet.
Install the package.
Configure Git by setting the
GIT_ASKPASS environment variable:
#!/bin/sh export GIT_ASKPASS='/usr/bin/ksshaskpass'
SSH_ASKPASSenvironment variable is set to ksshaskpass, then additionally setting
GIT_ASKPASSis not required.
Seefor alternatives and more details.
KDE Wallet for Chrome and Chromium
Chrome/Chromium has built in wallet integration. To enable it, run Chromium with the
--password-store=detect argument. To make the change persistent, see Chromium/Tips and tricks#Making flags persistent. (Setting CHROMIUM_USER_FLAGS will not work.)
Query passwords from the terminal
Instead of storing passwords in plain text files, you can manually add new entries in your wallet and retrieve them with kwallet-query.
For example, if you want to log into the Docker Hub registry with Podman, which supports getting the passwords from stdin with the
--password-stdin flag, you can use the following command to login:
$ kwallet-query -r folder_entry wallet_name -f folder_name | podman login docker.io -u dockerhub_username --password-stdin
This way, your password is not stored in any text file and neither is it stored in the terminal history file.