Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

initial clone on Linux fails when using server aliases with ssh_config (due to ssh-keyscan) #1238

Closed
megies opened this Issue Mar 30, 2013 · 5 comments

Comments

Projects
None yet
3 participants

megies commented Mar 30, 2013

I like to handle my ssh server configuration (on Linux) with ssh_config (~/.ssh/config). This helps with having one place to switch ssh server addresses/ports/aliases, rather than needing to adapt tons of places with hardcoded address values. However this causes the initial clone of a new project to fail (when using the alias) because it seems that ssh-keyscan is not looking up ssh server aliases in ssh_config.

I know this is not exactly a problem of SparkleShare itself but I nevertheless wanted to report the issue, as it can be puzzling and annoying. I did not find a solution on the net to make ssh-keyscan aware of ssh_config, so the workaround is to use the real address on the initial setup and then modify the sparkleshare config.xml afterwards to use the alias during regular operations.

Owner

hbons commented Apr 5, 2013

i don't know how to go about addressing this... maybe it's better to file a bug against OpenSSH and see if they want to implement your described behaviour? (i do agree that ssh-keyscan should pick up the aliases)

@hbons hbons closed this Apr 5, 2013

horazont commented Jun 1, 2013

Could this issue maybe be reopened so that it's easier to find?

Owner

hbons commented Jun 1, 2013

@horazont i don't see this as an issue in SparkleShare, so i don't see a reason to reopen it.

horazont commented Jun 1, 2013

Of coures it's not an issue in SparkleShare, but thats not obvious for the user. I though it might be helpful to have it quick-and-easy to find. Or maybe create a “Known Problems” section in the README.md file?

Owner

hbons commented Jun 1, 2013

@horazont i'd rather put effort in getting this thing resolved with OpenSSH. maybe you can report it upstream?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment