Thanks for investigating. At minimum, I think sss_ssh_knownhostsproxy
is going to need to provide a -4 flag for it to be possible to make that
work correctly. After that, it might be necessary to either mangle the
configured ProxyCommand by hand or to somehow extend the ProxyCommand
mechanism to
I've figured out that it is caused by this line in /etc/ssh/ssh_config
ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h
This was put there by the freeipa installer (ipa-client-install), so I
guess this is a freeipa or sssd bug.
--
You received this bug notification because you are a membe
Although it could still be a bug in ssh if ssh doesn't do ProxyCommand
correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1687482
Title:
-4 flag doesn't work
Statu
I'd suggest using "ssh -v" rather than relying on the "Last login:"
output. For instance:
$ ssh -v -Snone riva : 2>&1 | grep 'Connecting to'
debug1: Connecting to riva.pelham.vpn.ucam.org
[2001:8b0:bff2:eb14:6a05:caff:fe12:71bf] port 22.
$ ssh -4v -Snone riva : 2>&1 | grep 'Connecting to'
I'm running xenial. After I saw your comment I tried it on zesty and
have yet to run into this bug on zesty. I haven't tried in the same
environment yet though, I can try that later this week as well as get an
apport-collect done.
As you can see below, the last login reports an ipv6 address. I
Without a sophisticated ipv6 setup I tried the most trivial.
# ssh ip6-localhost
The authenticity of host 'ip6-localhost (::1)' can't be established.
[...]
root@zesty-test:~# ssh -4 ip6-localhost
The authenticity of host 'ip6-localhost (127.0.0.1)' can't be established.
As you can see the -4 succ
6 matches
Mail list logo
