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

algorithm for locating known_hosts differs from the "real" ssh #66

Closed
crosser opened this issue Apr 21, 2012 · 0 comments
Closed

algorithm for locating known_hosts differs from the "real" ssh #66

crosser opened this issue Apr 21, 2012 · 0 comments

Comments

@crosser
Copy link

crosser commented Apr 21, 2012

the "real" ssh uses the .ssh directory that is located under the "home" which is determined from getpwuid(get[e?]uid()). On the other hand, paramico apparently consults the $HOME/.ssh/known_hosts. And if you changed $HOME (which I did in the cronjob script) paramico does not find the known_hosts file.

By the way, the message that is issued in this case is rather confusing:

ssh connection to x failed: Unknown server x

which looks as if it could not resolve the server name. It would be much better if it said "No public key known for server x" or something like that.

Related duplicity bug: https://bugs.launchpad.net/duplicity/+bug/965017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants