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

docs: Configuration, known_hosts - is a little light. #3

Open
CarlFK opened this issue Apr 4, 2021 · 1 comment · May be fixed by #4
Open

docs: Configuration, known_hosts - is a little light. #3

CarlFK opened this issue Apr 4, 2021 · 1 comment · May be fixed by #4

Comments

@CarlFK
Copy link

CarlFK commented Apr 4, 2021

This might be a debian packing problem, but the docs for this one item seem to be missing a bit.

https://github.com/daradib/sidedoor#configuration

known_hosts: SSH host key of the remote server.

it would be nice to know what dir and permissions, and how to get the key using ssh-keyscan.

@e-gaulue
Copy link

I agree 👍

rfjakob added a commit to rfjakob/sidedoor that referenced this issue Oct 15, 2022
Just having gone through the process of installing, configuring
and debugging sidedoor, this commits tries to make a few spots
in the README clearer to make it easier for the next person.

It also mentions that you should set "ClientAliveInterval 30"
on the server side. This is a footgun that I hit when testing
sidedoor: Without it, a hung ssh session can block the port
and the remote server for a long time (days? hours?), making
the tunnel unusable.

Fixes daradib#3
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

Successfully merging a pull request may close this issue.

2 participants