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

Could not unlock ssh private key. Wrong password or password not available for cron. Reopened. #1985

Open
casimir7 opened this issue Dec 29, 2024 · 2 comments
Labels
Feedback needs user response, may be closed after timeout without a response

Comments

@casimir7
Copy link

This is the same issue as #1198. I reopen it here following advice by @buhtz.

Symptom:
When trying to access a(n encrypted) snapshot directory via ssh, the ssh key cannot be unlocked despite giving the correct password. The exact error message is the one in the title.

Things I have tried so far:

  • Re-installing BiT and starting with a fresh configuration did not solve the problem.
  • Checking that ssh-add /home/$user/.ssh./id_rsa works and that ssh-add -l lists the added key.
  • Checked that I can ssh into the remote location that BiT cannot access.

Information requested by @buhtz
I run BiT in normal user mode, not in root mode (which always worked until now).
ls -l gives the following permission info on my keys:

-rw-------. 1 $user $group 2675 Sep  2  2022 id_rsa
-rw-r--r--. 1 $user $group  585 Sep  2  2022 id_rsa.pub

Thanks for your time!

@TriplEight
Copy link

TriplEight commented Jan 7, 2025

Moreover, this prevents UI from opening. (also it dumps core)

Repro with screenshots
  1. run backintime-qt any way
  2. Fill the passphrase
    .
  3. Then nothing seemingly happens, only these processes (I assume this was the automatic part from https://backintime.readthedocs.io/en/latest/settings.html#ssh). Screenshot From 2025-01-07 13-31-27 The second process reappears some times, but UI won't ever appear. Relaunching BIT won't help.
  4. Only upon killing the first process you will get these windows:

    And then UI finally appears.

But the bug remains. Changing the keys (trying new ones too) won't help, it will produce the windows from p1 and p4.

@buhtz buhtz added this to the 1.6.0 (upcoming release) milestone Jan 16, 2025
@buhtz
Copy link
Member

buhtz commented Feb 4, 2025

Sorry guys, I am not able to reproduce this. You have to help me here with it.
Please provide full and detailed steps on a fresh VM how to reproduce this problem.

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

No branches or pull requests

3 participants