I’ve never seemed to be able to get ssh-agent to save my ssh-key passphrase, so I end up having to enter it every time I try to push to github.
I run fedora server on my homelab and I don’t have to enter my passphrase once I added it to my ssh-agent. I haven’t seen this mentioned anywhere so I wonder if it’s just me.
Or maybe I’m the only person using passphrases?
I’m getting a similar issue on Bluefin. When I enter a dev container or try to push changes, the ssh-agent popup appears a couple of times. I can cancel and the operation proceeds, but it’s odd.
My intuition is that the bluefin has the same cause.
I suspect that it has something to do with the agent using immutable storage and that there may be a way to configure the agent to use persistent storage.
I prefer not to do some kind of rpm-ostree layer just for the passphrase.
In the meantime, I’ve used the workaround found in this issue: SSH_ASKPASS set to non-existent /usr/libexec/openssh/gnome-ssh-askpass on GNOME BlueFin · Issue #3975 · ublue-os/bluefin · GitHub Basically, add this to your shell config: unset SSH_ASKPASS SUDO_ASKPASS
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.