-
Notifications
You must be signed in to change notification settings - Fork 203
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
Ubuntu 20.04 and 22.04 SSH encrypted issue #1379
Comments
I'm not the pro in that topic but I assume you will find your problem here in the README section about known problems. Please report back if you solved your problem or have further questions. |
buhtz
added
the
Feedback
needs user response, may be closed after timeout without a response
label
Nov 29, 2022
It was not easy as I'm not an expert of keyring but at the end I did it!
I followed issue #1321 (Using KDE Wallet works at 2nd attempt only #1321) until the last comment in order to modify the code in backintime/common/tools.py and now works.
Thanks,
Luca
Luca Bascetta, PhD.
Associate Professor
Chair of the Agricultural Engineering Study Programme
Politecnico di Milano
***@***.***
bascetta.deib.polimi.it<http://bascetta.deib.polimi.it>
[cid:c39a46ca-5c3b-423c-9492-304e179aa35f]
…________________________________
Da: buhtz ***@***.***>
Inviato: martedì 29 novembre 2022 15:41
A: bit-team/backintime ***@***.***>
Cc: Luca Bascetta ***@***.***>; Author ***@***.***>
Oggetto: Re: [bit-team/backintime] Ubuntu 20.04 and 22.04 SSH encrypted issue (Issue #1379)
I'm not the pro in that topic but I assume you will find your problem here in the [README section about known problems (https://github.com/bit-team/backintime#known-problems-and-workarounds).
Please report back if you solved your problem or have further questions.
—
Reply to this email directly, view it on GitHub<#1379 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK243X7RNG33DD3E44AJRILWKYIYXANCNFSM6AAAAAASORP3EU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
buhtz
removed
the
Feedback
needs user response, may be closed after timeout without a response
label
Nov 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting with Ubuntu 20.04 and now with 22.04 I have an issue using SSH encrypted.
Though there is no password for the private key and the encryption password is in back-in-time configuration (and cache password for cron is selected), every time I run the program two windows to ask me for the private key and the encryption password appear. The same happens when the program is started by cron.
The text was updated successfully, but these errors were encountered: