Skip to content
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

Open
dkebler opened this issue Nov 10, 2018 · 5 comments

Comments

@dkebler
Copy link

dkebler commented Nov 10, 2018

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)

@dkebler dkebler changed the title passphrase for ssh private key not being saved across reboot passphrase for ssh private key not being saved across reboot - support for key-agent Nov 19, 2018
@buhtz
Copy link
Member

buhtz commented Sep 26, 2022

@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.

@aryoda
Copy link
Contributor

aryoda commented Oct 7, 2022

@dkebler Did you enable the checkbox "Save Password to Keyring" in the settings GUI (General > Mode: SSH)?

This requires using a keyring backend supported by BiT and some configuration (see #990 or #1321)...

@emtiu emtiu added Bug Feedback needs user response, may be closed after timeout without a response labels Oct 7, 2022
@buhtz buhtz added this to the 1.3.5 / 1.4.0 milestone Mar 19, 2023
@buhtz
Copy link
Member

buhtz commented Mar 19, 2023

Is this a duplicate of #1146? If so can we close this issue then?

@aryoda
Copy link
Contributor

aryoda commented Mar 19, 2023

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:

  • The password can be stored in the user keyring. The keyring is unlocked with the users password during login.
  • When running a scheduled backup-job (via cron) while the user is not logged in, the keyring is not available.
  • For this case (cron job with user not logged in), the password can be cached in memory by Back in Time.
  • The cached password is lost after a reboot (AFAIR)

We should somehow make this more obvious in the GUI in the future.

@aryoda
Copy link
Contributor

aryoda commented Mar 19, 2023

Possibly related to #1308

@buhtz buhtz removed the Feedback needs user response, may be closed after timeout without a response label Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants