Bug#175928: libc6: dns broken w/ socksify ssh
Package: libc6
Version: 2.3.1-9
Severity: normal
## ssh via socks is unable to resolve my hostname
dannf@hazel:~$ socksify ssh home.dannf.org
ssh: home.dannf.org: Name or service not known
## but the system can
dannf@hazel:~$ host home.dannf.org
home.dannf.org A 12.252.80.98
## and telnet can, under socks
dannf@hazel:~$ socksify telnet home.dannf.org 22
Trying 12.252.80.98...
Connected to 12-252-80-98.client.attbi.com.
Escape character is '^]'.
## and i can socksify ssh if i specify the IP
dannf@hazel:~$ socksify ssh 12.252.80.98
Linux home 2.4.18sparc #1 Sun Sep 15 22:31:51 MDT 2002 sparc unknown
Most of the programs included with the Debian GNU/Linux system are
...
dannf@home:~$
I'm using ssh 3.5p1-3. I tried reverting to 3.4p1, but still had the same
issue. I'm using dante-client 1.1.13-1. This also exists on ia64, fwiw.
So, as I see it, this could just as likely be a bug in either ssh,
libc6 & libc6.1, or dante-client, so please reassign as necessary.
I've verified that this problem exists on 4 different i386 boxes running sid.
However, there is a fifth i386 box running the same versions of these packages
that works just fine. woody machines pointing at the same dns/socks servers
work fine.
On one of the 4 that show this problem, adding an entry for the target host to
/etc/hosts fixed the problem. (I couldn't check the other 3).
Removing the entry broke it again. This, and the fact that I first noticed
the problem after a recent libc6 upgrade, is why I chose to file the bug
against libc6.
## my nsswitch.conf is pristine
dannf@hazel:~$ grep ^hosts /etc/nsswitch.conf
hosts: files dns
I tried rebuilding both dante-client and ssh against the headers on the
system, but didn't see a change.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux hazel 2.4.19-686-smp #1 SMP Tue Nov 19 00:58:50 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-7 The Berkeley database routines [gl
-- no debconf information
Reply to: