![]() Make sure other providers like gnome-keyring-daemon are not running.sudo apt install libsecret-tools for testing and command line tooling.Furthermore, your passwords are not distributed over multiple password safes. If you however trust the software you have installed and you are somewhat lazy, then this is a pretty nice way of managing secrets, while at the same time being limited to the entries/programs you configure to make use of it and the timeframe during which your database is unlocked. A drawback of this libsecret solution is that there is no authentication or verification whithin this API. This is in reference to KeePassXC’s libsecret integration. While searching for a solution, I found a very nice way to automatically unlock my GPG key, without even copying the password into the clipboard. Only the OK and Cancel buttons, as well as the text input field remain responsive, and nothing else. However since the update now, mouse input is blocked as well. I could not use shortcuts, but oh well - at least I don’t need to remember the password. ![]() Fetching the password for a GPG key from a personal KeePassXC database was thus still possible. When encrypting or signing emails, or when signing git commits, the keyboard input for the whole desktop used to be blocked, but still allowed mouse input. Since the update to (K)ubuntu “focal fossa”, the GPG pinentry dialog behaves a bit differently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |