Why is bitwarden trying to integrate with kwallet?
Kwallet seem to be a credential/password manger in it’s own right, though I never used it nor installed it.
Feb 09 22:33:15 hostname xdg-desktop-por[1994]: Backend call failed: The name org.freedesktop.impl.portal.desktop.kwallet was not provided by any .service files
Feb 09 22:33:15 hostname flatpak[32003]: 22:33:15.468 › [NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden redacted_accessTokenKey
Feb 09 22:33:15 hostname flatpak[32003]: 22:33:15.474 › SetAccessToken: storing encrypted access token in secure storage failed. Falling back to disk storage. Error: New Access token key unable to be retrieved from secure storage.
What are the security considerations of bitwarden “Falling back to disk storage” from whatever it was trying to do with kwallet?
Correction, kwallet6 was already preinstalled on my system so my claim earlier is thus incorrect.
1 Like
So I opened K wallet manager and learned that kwallet must be enabled before use, something I was not aware of.
After enabling it the above errors are gone, though i get this:
NAPI] [INFO] desktop_core::password::password: falling back to get legacy Bitwarden_auto redacted-random-string_user_auto
after search some more it appears that kwallet is a “secrect service” (A way to manage password, SSH keys and other secrets on linux systems) and bitwarden utilizes it as a way to unlock a locked (not logged out) vault.
So after integrating with kwallet bitwarden gets a “Unlock with system authentication” button.
If i try to enable it i get “Due to the installation method, biometrics support could not be automatically enabled. Would you like to open the documentation on how to do this manually?”
Link: Unlock With Biometrics | Bitwarden (It has no relevant information, and seems to be about biometric unlock, something that kwallet does not even support)
Anyway, I now think I know what the integration is intended for, a way to unlock the bitwarden vault without having to type the password.