Control: tag -1 + upstream Control: severity -1 minor Hi,
Michael Gold wrote (29 Aug 2015 16:35:00 GMT) : > An strace reveals it was trying to connect to 127.0.0.1:9050, not to the > internet; code inspection reveals this to be a hard-coded SOCKS address. > The preceding "Downloading https://www.torproject.org…"; message makes it > look like it was www.torproject.org that rejected the connection. I agree this is a UX problem, thanks for reporting it to Debian. Do you want to report it upstream[0]? (I don't remember if the upstream author tracks the Debian BTS.) Note that I'm downgrading the severity a bit, because this only affects users who have manually configured their system-wide tor daemon to *not* listen on the default SOCKS port. I expect them to be power-users who may be able to correlate "Updating over Tor" failing with "I have a custom, non-default Tor configuration that torbrowser-launcher was not able to guess". [0] https://github.com/micahflee/torbrowser-launcher/issues/ Cheers, -- intrigeri
