It is possible to use KeePassXC as the system keyring.

Here's how I set things up on my system using i3wm with no display manager.

• Stop gnome-keyring if it's installed.
  • pgrep -l gnome
  • pkill pid
• Create a new group in the database that will hold the passwords used for the keyring
• Tools > Settings > Secret Service Integration >
  • Enable KeepassXC Freedesktop.org Secret Service integration
• Database > Database Settings > Secret Service Integration > Expose entries under this group:
  • Select the new group

https://unix.stackexchange.com/questions/271661/disable-gnome-keyring-daemon

Create 3 .desktop files and place them in ~/.config/autostart:

gnome-keyring-pkcs11.desktop

[Desktop Entry]
Hidden=true

gnome-keyring-secrets.desktop

[Desktop Entry]
Hidden=true

gnome-keyring-ssh.desktop

[Desktop Entry]
Hidden=true

See secret-tool for more info.

{attribute} {value} references key:value pairs stored under the Advanced section of an Entry.

secret-tool store --label='My Label' {attribute} {value} {attribute2} {value2} [...]

secret-tool lookup {attribute} {value} {attribute2} {value2} [...]

See keyring for more info.

import keyring

keyring.get_credential('SERVICE', 'USERNAME')
keyring.get_password('SERVICE', 'USERNAME')

keyring set SERVICE USERNAME
keyring get SERVICE USERNAME
keyring del SERVICE USERNAME

There are different fields that are stored in the Advanced > Attributes section of each entry.

You can create your own key:value pairs for easier access and searching of specific entries.

Here's a couple examples:

Title: Nextcloud Desktop
Username: username
Password: *******
URL: https://path.to.nextcloud

Type: Password
Use: Saved password or login
server: Nextcloud
type: plaintext
user: username:https://path.to.nextcloud/:0

You can configure access to remote filesystems for browsing in Thunar.

• The double // is not a typo.
• The password field should contain the password for the ssh key.

Title: username@hostname//home/username/.ssh/key
Username: username
Password: ********

authtype: publickey
object: /home/username/.ssh/key
protocol: sftp
server: hostname
user: username
xdg:schema: org.gnome.keyring.NetworkPassword

Entries created with keychain have the following attributes

Title: Password for 'username' on 'service'
Username: username
Password: ********

application: Python keyring library
service: twitter
username: username

Given the above information, when creating an entry for use by the keyring I would recommend creating the following attributes every time for each entry:

• service: SERVICE
• username: USERNAME

This way, it will be available to python3-keyring as well.

secret-tool store --label='My Label' service SERVICE username USERNAME
Password:

• https://www.cogitri.dev/posts/03-keepassxc-freedesktop-secret/
• https://www.reddit.com/r/linux/comments/ehfhud/keyring_alternative_access_keepassxc_entries_of/
• https://rtfm.co.ua/en/keepass-an-mfa-totp-codes-a-browsers-passwords-ssh-keys-passwords-storage-configuration-and-secret-service-integration/
• https://isamert.net/jekyll/update/2018/10/05/automatize-your-logins-with-gnome-keyring-and-keepassxc.html
• https://rtfm.co.ua/en/keepass-ssh-keys-passwords-storage-and-decryption-on-linux/