-
Notifications
You must be signed in to change notification settings - Fork 0
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
Error adding known keys #6
Comments
As a parallel comment. It doesn't seem entirely correct to ignore errors here: ansible-backuppc-client/tasks/ssh.yml Line 43 in 4b71900
the next task depends on the correct definition of that variable. |
I don't think this error is systematic, but it's good to test it in all the situations, because this task is now supposed to add or update the key. In which situation do you have this error? Didn't you previousely accessed the server with ssh command?
Indeed, I noticed that this module stores in clear the hostname in the known_hosts. In old versions, ssh used to update this file in this way, but since quite a time it does hash the hostname (for privacy, better not knowing what site people visit...). So certainly you are right, better to always hash the hostname. But I would like to understand what happend, because I don't see where is the "hashed host field in supplied key". |
You're right. What I should have put here is |
I'm having an error in this task that I still can't fully understand but I can solve
ansible-backuppc-client/tasks/ssh.yml
Line 45 in 4b71900
From the previous task, the
ssh_known_host_results
variable is set with the following value:However I get the following error:
Indicating
hash_host: yes
in the task (default value isno
) I don't get an error and can complete the role execution.Note: I am running on LXC containers of the same Debian Buster image on both sides
The text was updated successfully, but these errors were encountered: