-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Use ResolveCommand hostname when creating ssh config #244
Comments
Hi @herver, thank you for your feedback Can you confirm me that the expected behavior is that Example: hosts:
"osd.[0-9]*.ceph1":
ResolveCommand: /bin/sh -c "ceph --cluster ceph1 osd find $(echo %h | sed -E 's/osd.([0-9]+).ceph1/\1/') | jq -r .crush_location.host" Host osd.42.ceph1
Hostname: 1.2.3.4 (result of the ResolveCommand)
Host osd.1337.ceph1
Hostname: 5.6.7.8 (result of the ResolveCommand) |
Hi @moul, This is exactly what I would expect,
|
I suspect Kerberos authentication to look for an uncommented Before trying to run the I will try to setup a Kerberos test environment to give a try by myself |
I tried with both As you feared, it requires the |
Hello,
I'm trying to use assh in combination with kerberos authentication, and there is a small issue, here's my configuration:
The
ResolveCommand
returns the correct hostname, but when ssh is connecting to the machine, it mentions the hostname I type on the command line, and not the resolved one. This prevents SSH from using Kerberos authentication because the hostname provided by ASSH doesn't match any entry on the Kerberos database.The text was updated successfully, but these errors were encountered: