could this be the behavior for the default ssh key out of the box? in kde it would need a desktop file and env set: https://wiki.archlinux.org/title/KDE_Wallet#Using_the_KDE_Wallet_to_store_ssh_key_passphrases it could be extended to load all known keys as well.
+1
We're going to try to get this in place for F40, but also we want to make sure KWallet is a secrets service provider, so that we can stop shipping gnome-keyring...
Metadata Update from @ngompa: - Issue assigned to aleasto - Issue set to the milestone: Fedora Linux 40
Arch Wiki documentation on this: https://wiki.archlinux.org/title/KDE_Wallet
I don't know what sets it but SSH_ASKPASS is already /usr/bin/ksshaskpass
SSH_ASKPASS
/usr/bin/ksshaskpass
This is a bit weird imo because when you create a new ssh key it won't be added to kwallet until you logout and re-login
secrets API was tracked here: https://pagure.io/fedora-kde/SIG/issue/340
and it's still blocked on https://bugs.kde.org/show_bug.cgi?id=466197 for flatpaks
secrets API was tracked here: https://pagure.io/fedora-kde/SIG/issue/340 and it's still blocked on https://bugs.kde.org/show_bug.cgi?id=466197 for flatpaks
hey @aleasto it looks like https://bugs.kde.org/show_bug.cgi?id=466197 was fixed. what does that mean for https://pagure.io/fedora-kde/SIG/issue/340 ?
Login to comment on this ticket.