When it comes to managing passwords, there are several options available to you. Kubuntu Focus computers come with a couple of these pre-installed, but there are several others that you can find throughout the web.
KDE Wallet is the default password manager on Kubuntu systems. It stores passwords completely encrypted and unlocks upon login. All KDE applications integrate with this password manager, and it stores Wi-Fi passwords, file manager passwords, and other system passwords. It can also integrate really well with Google Chrome and other browsers.
One thing to note is that, by default, the KDE Wallet master password is the same as your user password. For this reason, if you ever change your user password, your KDE Wallet password will no longer unlock automatically upon login. Fixing this is as easy as adjusting the wallet settings:
System Settings > Account Settings
Wallet Preferences, make sure
[x] Enable the KDE Wallet Subsystemis selected
Launch Wallet Manager
Wallet Managerapp appears, click on the top-right button labeled
KeePassXC is a cross-platform, synchronizable, decentralized password management solution. It has plugins for Chrome (and other Chromium-based browsers), Firefox, and solutions exist for Android. We highly recommend this password solution. For many, it’s a great alternative to commercial services like LastPass and 1Password.
sudo apt install libsecret-tools). This provides the
Tools > Settings > Secret-Service-Integrationand check the
Enable KeepassXC Freedesktop.org Secret Service Integrationand click
Tools > Settings > Secret-Service-Integration, click the
Generaltab, and then in the
Exposed Database Groupstable, click the small pencil icon next to the database you want to host the secrets. This will show the
Database Settingsdialog, which has a Secret Service Integration section. Click on
Secret Service Integrationand then check the
Expose entries under this groupradio option. Select the group you created in the second step, and click
secret-tool store --label='Created from cli' account test, and then enter your desired password. You should be able to see this new credential in KeePassXC
Some forum posts recommend installing Gnome Keyring; however, this can interfere with the KWallet subsytem. For this reason, we strongly recommend you try to use KeePassXC instead.
KeePassXC’s database file can be synchronized via cloud sync services, such as Dropbox, Google Drive, OneDrive, ownCloud, Nextcloud, and others, which is the foundation for synchronizing across multiple devices. To learn more, visit the KeePassXC website.
Decentralized browser-based solutions exist as well, such as ownCloud and Nextcloud. These solutions require your own web server and adding the respective password management applications to the ownCloud and Nextcloud instances you run on those servers. For more information on these, see the links to the respective solutions.
Content will be added as needed.
This is a partial revision history. See the
git repository for all entries.
2022-03-21 06240af7Add KeePassXC libsecret advice
2021-10-10 5728326eReformat to 2-column
2021-09-22 dc862884Update link and headline colors
2021-08-23 681261b4Review and update codeblocks
2021-07-27 9e6157ceUpdate KWallet advice
2021-06-18 13c5e182First publication
We try hard to provide a useful solution validated by professionals. However, we cannot anticipate every situation, and therefore cannot guarantee this procedure will work for your needs. Always backup your data and test the solution to determine the correct procedure for you.
THIS SOLUTION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOLUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.