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

rsync does not work after adding new key #44

Open
pchampin opened this issue Oct 28, 2022 · 4 comments
Open

rsync does not work after adding new key #44

pchampin opened this issue Oct 28, 2022 · 4 comments

Comments

@pchampin
Copy link

When the Remarkable tablet is updated, the SSH server has a new key, which requires to update the known_hosts file on the client side.

Remy offers several options, the first one being, IIUC, to add a known_hosts file in ~/.config/remy, and use that one for SSH connection.

The problem is: once that is done, my rsync based config does not work anymore, because while Remy manages to SSH to the Remarkable, the subsequent rsync does not.

If there is a way to configure rsync to use ~/.config/remy/known_hosts instead of the default one, it should be used. Otherwise, the option to automatically add the new ket should have a big red warning "this will break your rsync based configs".

@bordaigorl
Copy link
Owner

Very good point!
I'll think of a fix

@bordaigorl
Copy link
Owner

Actually: this should not be happening!
The known_hosts file used for ssh connection should be the same used for invoking rsync.
Can you set "log_verbosity": "debug" in your config and check what the log says about known_hosts?

@bordaigorl
Copy link
Owner

For example: if you set the known_hosts setting in the source you are using, Remy would always try to use that one, regardless of the existence of the Remy-specific one.

@pchampin
Copy link
Author

Actually: this should not be happening!

Strange. Maybe I misdiagnosed the problem, sorry about that.

I can't reproduce the bug right now because I have updated by ~/.ssh/known_hosts in order to fix the problem. I tried to restore the old one, but this give me very strange behaviors, that I couldn't make sense of...

I did add "log_verbosity": "debug" to my config. On the next update, I will try to monitor carefully what happens, and keep the logs.

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