-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
passphrase for ssh private key not being saved across reboot - support for key-agent #949
Comments
@dkebler There is a new forming maintaining team and we do review all issues. Is this problem still relevant for you, can you reproduce it with a newer or the latest release? Did you find a solution? Tag: Feedback, Support, Documentation Good question but I don't have an answer to that because I don't use passphrased keys. |
Is this a duplicate of #1146? If so can we close this issue then? |
Perhaps. Or a documentation issue (the scenarios when to use the password cache vs the keyring is not that intuitive to understand and the restrictions are not quite obvious in the GUI IMHO): https://backintime.readthedocs.io/en/latest/settings.html#ssh Basically:
We should somehow make this more obvious in the GUI in the future. |
Possibly related to #1308 |
Running Ubuntu 18.04 and BIT 1.1.24
I set up several remote jobs via ssh and they all work only the passphrase for my private ssh key is not preserved across a reboot. Every time I reboot BIT pops a dialog for each of these remote jobs asking for the ssh key passphrase again despite checking the "cache" and "keyring" options.
How can I get BIT to really store my ssh key passphrase.
Alternatively if BIT supported key-agent via a the so)cket it there would be no need to use the passphrase (at least from active desktop session)
The text was updated successfully, but these errors were encountered: