Problems on ssh key unlocking

Asked by Mauro

I have a problem with SSH key unlocking. I have set up a profile for SSH remote backup and an SSH key used for password-less login to my NAS. I've set a passphrase to unlock this key and typed it into BIT settings dialog. I also checked both "save to keyring" and "save for cron", but what I observe is that whenever the scheduled job should start automatically, a prompt is shown to enter the passphrase to unlock the SSH key, I don't want this to happen, BIT should just work with no prompt!

Some more information. The profile is for a normal user (non-root). I'm using KDE, so the keyring service is performed by kwallet. My kwalltet does not have any password, so BIT should be able to access it with no need for me to enter the kwallet password either.
If I type the SSH key unlock passphrase, from that moment on BIT correctly does all its scheduled jobs without asking any more for the passphrase.

Am I missing something? I would just like to make BIT run automatically without any user intervention at all. Am I forced to create a new key without any passphrase?

Thanks in advance.

P.S.: a secondary problem is that if for whatever reason I type the passphrase wrong, from that moment on BIT does not ask for it any more and keeps on saying that the passphrase is wrong or that it is not available for cron. I couldn't find a way to make BIT request the passphrase again to correct the error.

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Mauro
Solved:
Last query:
Last reply:
Revision history for this message
Germar (germar) said :
#1

Hi Mauro,

Please install python3-secretstorage. Package dependencies were wrong for this. I'll fix this with next release.

After installing please run 'backintime --pw-cache stop'.

Regards,
Germar

Revision history for this message
Mauro (mauromol) said :
#2

Hi Germar,
I installed python3-secretstorage, ran backintime --pw-cache stop (the system said that the daemon was not running in that moment) and even reboot the system. Then, I waited for the next schedule to occur, but yet again BIT showed a prompt for the SSH key passphrase :-(

So, nothing has changed after installing python3-secretstorage, unfortunately.

Revision history for this message
Germar (germar) said :
#3

Hi Mauro,

Sorry that it took me so long for an answer. I somehow forgot this question.

It could be that this is related to bug #1431305. I'll focus on this the next days and hopefully be able to release a new version very soon where this is fixed, too.

Sorry again.

Revision history for this message
Mauro (mauromol) said :
#4

Hi Germar,
don't worry, you don't have a contract with me! :-D
Nevertheless I really appreciate your support and your work.

I'll keep an eye on that bug and try to update as soon as the new version is available.

Revision history for this message
Mauro (mauromol) said :
#5

It seems like the problem is actually solved by the fix to bug #1431305. Thank you! :-)