If you have a working #syncthing (syncthing-fork android is aalways killed in background) then #keepassdx and #keepassxc work very well.
Recently I overhauled my databases, merged all the sync conflicts to get all the random passwords I had missed. Works!
Btw, I think I dont even have syncthing setup
Mein #yubikey wird in #keepassxc nicht mehr erkannt bzw erkannt aber nicht mehr gelesen. 
#PCSC läuft. Hab das auch nochmal neu installiert. Aber hat nichts gebracht.
Hat jemensch eine Idee wie ich das fixen könnte? 
#eh22
![(base) robin@ms-li-n-16-013:~> keepassxc
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
YubiKey: Failed to establish PCSC context.
YubiKey: PCSC interface is disabled or not initialized.
(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.service
[sudo] password for root:
● pcscd.service - PC/SC Smart Card Daemon
Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: disabled)
Active: active (running) since Sat 2025-04-19 11:24:06 CEST; 1min 10s ago
Invocation: 9329d05718c84027830ea578a2c56af5
TriggeredBy: ● pcscd.socket
Docs: man:pcscd(8)
Main PID: 5026 (pcscd)
Tasks: 5 (limit: 18884)
CPU: 56ms
CGroup: /system.slice/pcscd.service
└─5026 /usr/sbin/pcscd --foreground
Apr 19 11:24:06 ms-li-n-16-013 systemd[1]: Started PC/SC Smart Card Daemon.
(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
Loaded: loaded (/usr/lib/systemd/system/pcscd.socket; enabled; preset: enabled)
Active: active (running) since Sat 2025-04-19 11:22:07 CEST; 3min 28s ago
Invocation: 5770cc7bcaed47f89f130f1d47cd9826
Triggers: ● pcscd.service
Listen: /run/pcscd/pcscd.comm (Stream)
CGroup: /system.slice/pcscd.socket
Apr 19 11:22:07 ms-li-n-16-013 systemd[1]: Listening on PC/SC Smart Card Daemon Activation Socket.](https://assets.chaos.social/media_attachments/files/114/363/943/390/192/001/original/7e989322ff605ce6.png "(base) robin@ms-li-n-16-013:~> keepassxc
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
YubiKey: Failed to establish PCSC context.
YubiKey: PCSC interface is disabled or not initialized.
(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.service
[sudo] password for root:
● pcscd.service - PC/SC Smart Card Daemon
Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: disabled)
Active: active (running) since Sat 2025-04-19 11:24:06 CEST; 1min 10s ago
Invocation: 9329d05718c84027830ea578a2c56af5
TriggeredBy: ● pcscd.socket
Docs: man:pcscd(8)
Main PID: 5026 (pcscd)
Tasks: 5 (limit: 18884)
CPU: 56ms
CGroup: /system.slice/pcscd.service
└─5026 /usr/sbin/pcscd --foreground
Apr 19 11:24:06 ms-li-n-16-013 systemd[1]: Started PC/SC Smart Card Daemon.
(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
Loaded: loaded (/usr/lib/systemd/system/pcscd.socket; enabled; preset: enabled)
Active: active (running) since Sat 2025-04-19 11:22:07 CEST; 3min 28s ago
Invocation: 5770cc7bcaed47f89f130f1d47cd9826
Triggers: ● pcscd.service
Listen: /run/pcscd/pcscd.comm (Stream)
CGroup: /system.slice/pcscd.socket
Apr 19 11:22:07 ms-li-n-16-013 systemd[1]: Listening on PC/SC Smart Card Daemon Activation Socket.")
![(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.service
● pcscd.service - PC/SC Smart Card Daemon
Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: disabled)
Active: active (running) since Sat 2025-04-19 11:24:06 CEST; 9min ago
Invocation: 9329d05718c84027830ea578a2c56af5
TriggeredBy: ● pcscd.socket
Docs: man:pcscd(8)
Main PID: 5026 (pcscd)
Tasks: 5 (limit: 18884)
CPU: 258ms
CGroup: /system.slice/pcscd.service
└─5026 /usr/sbin/pcscd --foreground
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000055 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00248831 ../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000138 ../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000008 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00359199 ../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000026 ../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000003 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:48 ms-li-n-16-013 pcscd[5026]: 00609843 ../src/winscard_svc.c:404:ContextThread() Communication protoco](https://assets.chaos.social/media_attachments/files/114/363/943/384/044/245/original/b928b23615b56bea.png "(base) robin@ms-li-n-16-013:~> sudo systemctl status pcscd.service
● pcscd.service - PC/SC Smart Card Daemon
Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: disabled)
Active: active (running) since Sat 2025-04-19 11:24:06 CEST; 9min ago
Invocation: 9329d05718c84027830ea578a2c56af5
TriggeredBy: ● pcscd.socket
Docs: man:pcscd(8)
Main PID: 5026 (pcscd)
Tasks: 5 (limit: 18884)
CPU: 258ms
CGroup: /system.slice/pcscd.service
└─5026 /usr/sbin/pcscd --foreground
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000055 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00248831 ../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000138 ../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000008 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00359199 ../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000026 ../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Apr 19 11:29:47 ms-li-n-16-013 pcscd[5026]: 00000003 ../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Apr 19 11:29:48 ms-li-n-16-013 pcscd[5026]: 00609843 ../src/winscard_svc.c:404:ContextThread() Communication protoco")
#Syncthing is setup as well as #KeepassXC and #Rofi, I even got back my #Joplin notes too
@Framasoft
Je vois que je ne suis pas le seul à passer par KeepassXC. 
Avec ça le client Electron de Mattermost n’a aucun avantage par rapport au client Web, à moins d’être dépourvu d’un navigateur Web.
À voir si je change d’avis quand des clients alternatifs apparaîtront. Un client en TUI par exemple.
@TeachrDigital Und ziehst du dann auch mit deinen Passwörtern von 1Password weg? Also zu #Bitwarden, #Vaultwarden oder #KeePassXC? Oder irgendeinen anderen FOSS Passwortmanager?
@keepassxc
Are there ways for system administrators in a business environment to set system-wide minimum requirements for the master password of KeePassXC-databases?
Otherwise, users could secure valuable collections of access data with a password such as "1234"...
Where can I find documentation about this topic?
You are using #keepassxc and enabled the secret storage backend? Then you want to set the following in `~/.config/kwalletrc`:
```
[Migration]
MigrateTo3rdParty=true
[KSecretD]
Enabled=false
```
https://notmart.org/blog/2025/04/towards-a-transition-from-kwallet-to-secret-service/
I don't know who needs to read this, but if you're an #emacs and #keepassxc user frustrated that their libsecret api specs don't line up, you can accommodate Emacs in KeePassXC by adding host, port, and user attributes under the advanced settings for an entry.
There's a shim out there to reshape Emacs' auth-source libsecret spec to match KeePassXC's, but it's easier the other way around.
@dmnelson , @me, @esparta thanks for your suggestions about #keepassxc , the #qrcode generation feature really made my migration and backups easy.
@yvan As others said, it's #KeepassXC if you want to take care of your own data and backups. I wrote a guide on how to install and use it effectively, if you or others are interested:
@TeddyTheBest probably because there is no #affiliate link for #KeepassXC 
Next-Level Security with KeePassXC!
https://air-academy.org/you-need-to-use-a-password-manager/
Struggling to manage complex passwords? KeePassXC stores, protects, and autofills your credentials securely—no cloud required! Take control of your digital security today.
#cybersecurity #privacy #infosec #password #keepassxc
Güvenli parola oluşturmak ve yönetmek mi istiyorsunuz? İşte KeePassXC'yi nasıl kullanacağınız hakkında bir kılavuz! 
Tüm parolalarınızı tek bir yerde saklayın ve güvende tutun. Daha fazlasını öğrenin ve hemen başlayın! #KeePassXC #ParolaYöneticisi #Güvenlikİpuçları
https://ssd.eff.org/tr/module/nasil-keepassxcyi-kullanmak #turkey #türkiye
Just finished migrating all my TOTP codes from google authenticator to #freeOTP+ (and backup in a #keepassxc vault)
Not the most fun thing, but that's another #google "service" removed from my life. 
@pixeldorf Sollte gehen, die meisten Clients können mehrere Tresore öffnen (#KeePassXC auf jeden Fall, inkl. Drag-and-drop von einem zum anderen).
@pixeldorf Halt dich an das #KeePass-Format. Ein guter Client für Desktops ist #KeePassXC, für iOS #KeePassium, für Android #Keepass2Android. Der große Vorteil ist, dass du bei Bedarf jederzeit den Client wechseln kannst.
@pixeldorf schau dir mal https://www.kuketz-blog.de/empfehlungsecke/#passwort-manager an. vielleicht hilft dir das. ich verwende schon seit Jahren #KeepassXC und hab nur gute Erfahrungen gemacht
Zu sicheren Passwörtern wechseln schwer gemacht, zu bearbeitende Einträge 2 und 3: Railcolor News weist einem Passwörter zu, nicht änderbar. nu3.ch lässt das nur über Passwort zurücksetzen zu.
oh, hatte gar nicht gewusst, dass #KeepassXC auch auf einem lokalen Pfad #Backups speichern kann, selbst wenn die #Datenbank woanders liegt.
Das hilft.
Y'all, I'm kind of struggling with my switch to #KeePassXC from #1Password. 1Password allowed me to save credit card information then easily use it while browsing. #KeePass doesn't really seem to have that option. No big deal, I'll just use Firefox to store credit card info instead. Only problem, it doesn't seem to save the code, so what good does that do? I have to get up and go find the card or save the code somewhere else? Not ideal. Meh.
