Hi, On Tue, Dec 08, 2015 at 11:15:16PM +0100, Petter Reinholdtsen wrote: > The error message is not easy to understand, and I was unable to > understand that this was the same as this error when using the normal > http transport: > > Err http://http.debin.net jessie Release.gpg > Something wicked happened resolving 'http.debin.net:http' (-5 - No > address associated with hostname) (not that this would be my preferred error message in apt as "something wicked happened" isn't that great.) > Would it be possible to change the message from apt-transport-tor to > explain that the hostname is unknown or missing in DNS or something > instead of the "Can't complete SOCKS5 connection to 0.0.0.0:0" message? The response is nowadays (for 'http' – it is still the same for 'https', where it is the responsibility of curl to report such errors): Err:197 tor+http://vwakviie2ienjx5t.onion/debian sid InRelease SOCKS proxy socks5h://localhost:9050 didn't grant the connect to 0.0.0.0:0 due to: TTL expired (6) If you wonder where the 0.0.0.0:0 comes from: That is Tor's choosing. It has also chosen to represent such errors with errorcode 6 which is defined by the SOCKS5 RFC to be a "TTL expired" error which is techncically correct I guess given that there is a long timeout involved. Given the feedback we get from the SOCKS proxy (which Tor is just one possible implementation of) I am not sure we can do particularily better than this without guessing and overriding Tors choices. So I would strongly advice to not make typos I guess… ;) Do you have any specific ideas? Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature