Package: tor Version: 0.3.0.1-alpha-1 Severity: normal Control: block 849845 with -1 Control: affects -1 dirmgnr
consider the following two commands: curl --socks5-hostname 127.0.0.1:9050 http://www.google.com curl --socks5-hostname 127.0.0.1:9050 http://ipv6.google.com www.google.com has A and AAAA records. ipv6.google.com has only AAAA records. the first command shows me the body of the 302 redirection. the second command sends this line to stderr: curl: (7) Can't complete SOCKS5 connection to 0.0.0.0:0. (4) and returns error code 7. afaict, this is true for every connection to an IPv6 address through tor. I'm not sure how to debug, but this appears to be what's causing the tor+ipv6 failures for dirmngr over on https://bugs.debian.org/849845, so i'm marking this as blocking that bug. Any suggestions for debugging? can you reproduce the problem? Should i be trying to do this some other way? --dkg -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tor depends on: ii adduser 3.115 ii init-system-helpers 1.46 ii libc6 2.24-8 ii libevent-2.0-5 2.0.21-stable-2.1 ii libseccomp2 2.3.1-2.1 ii libssl1.1 1.1.0c-2 ii libsystemd0 232-8 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-4 Versions of packages tor recommends: pn logrotate <none> ii tor-geoipdb 0.2.9.8-2 ii torsocks 2.2.0-1 Versions of packages tor suggests: pn apparmor-utils <none> pn mixmaster <none> pn obfs4proxy <none> pn obfsproxy <none> ii socat 1.7.3.1-2 pn tor-arm <none> ii torbrowser-launcher 0.2.6-3 -- no debconf information
