-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
the hostname could not be number #674
Comments
Hi! I am running into the same problem. Has it been solved? |
This just started happening for me, today... Could have been post-homebrew-upgrade, but unfortunately wasn't paying enough attention to notice when it broke. EDIT: The hostname is supposed to be commented out, i realized -- the actual connection is made using
ssh (using a config to bypass assh) works fine:
other tools (e.g, netcat) also connect successfully. I'm running assh 2.16.0, freshly re-installed with Other IP addresses seem to connect fine. This happens to (as far as I can tell) only affect sshing to the IP address which is also the default gateway for my host's primary IP address... 😕 |
Turns out, in my case, this is golang running afoul of a newer macOS security mechanism. I guess this will be fixed when a fixed go compiler is used to build assh. (for homebrew) |
sample from generated ~/ssh/.config
log
why the hostname is # HostName: 192.168.2.101 in generated ~/.ssh/config, not hostname 192.168.2.101, Can I customize the template before building config?
The text was updated successfully, but these errors were encountered: