Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Can't update apt with apt-transport-tor

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
SavoyRoad
Posts: 9
Joined: 2016-02-27 15:20

Can't update apt with apt-transport-tor

#1 Post by SavoyRoad »

I am trying to set up apt through Tor. Documentation is pretty sparse from what I could find, but from what I gather, all that needs to be done is install apt-transport-tor and edit sources.list with 'tor+http*.onion' (and obviously the correct hostnames from onion.debian.org). Once set up and I try an apt-update, I get the following error message after a 5-10 second hangup on trying to connect to socks5h://localhost:9050:

Code: Select all

Waiting for the SOCKS proxy socks5h://localhost:9050 to first part of response timed out [IP: 127.0.0.1 9050]
The logs have no error messages, showing the socks listener open on port 9050 and with the following line towards the end of the relevant info:

Code: Select all

Tor has successfully opened a circuit. Looks like the client functionality is working.
Bootstrapped 100%: Done 
Is there an edit I have to do first to /etc/tor/torrc that I'm unaware of?

Full apt error output: https://privatebin.net/?8e568c5cb48f055 ... 70LnDUwfg=
sources.list: https://privatebin.net/?ded4d7ad7d4795b ... E9ncKnlrY=

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Can't update apt with apt-transport-tor

#2 Post by Head_on_a_Stick »

I've never tried this but have you followed all of the instructions in /usr/share/doc/apt-transport-tor/README.md.gz?
deadbang

SavoyRoad
Posts: 9
Joined: 2016-02-27 15:20

Re: Can't update apt with apt-transport-tor

#3 Post by SavoyRoad »

I read through the README and modified my sources.list slightly to just this.

Code: Select all

deb tor+http://vwakviie2ienjx6t.onion/debian testing main contrib non-free 
deb-src tor+http://vwakviie2ienjx6t.onion/debian testing main contrib non-free  
The only issue I'm seeing now is being unable to connect through to the proxy.

Code: Select all

Err:3 tor+http://vwakviie2ienjx6t.onion/debian testing InRelease                              
  Waiting for the SOCKS proxy socks5h://localhost:9050 to first part of response timed out [IP: 127.0.0.1 9050]
Reading package lists... Done                              
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: Failed to fetch tor+http://vwakviie2ienjx6t.onion/debian/dists/testing/InRelease  Waiting for the SOCKS proxy socks5h://localhost:9050 to first part of response timed out [IP: 127.0.0.1 9050]
W: Some index files failed to download. They have been ignored, or old ones used instead.
I also ran nmap on localhost to double check if Tor's 9050 port is open, and it correlates to what syslog showed from my last post. It looks like it might be an issue with Tor itself then instead of the apt transport protocol?

EDIT: Just tried setting my browser to use the Tor socks proxy and it connects perfectly fine. However, the logs show different error messages like these:

Code: Select all

Aug 14 13:47:09 $HOSTNAME Tor[25362]: We tried for 15 seconds to connect to '[scrubbed]' using exit $EXIT at XXX.XXX.XXX.XXX. Retrying on a new circuit.
Aug 14 13:47:45 $HOSTNAME Tor[25362]: Tor has not observed any network activity for the past 71 seconds. Disabling circuit build timeout recording.
Aug 14 13:47:48 $HOSTNAME Tor[25362]: Our IP address has changed.  Rotating keys...
Aug 14 13:47:49 $HOSTNAME Tor[25362]: Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 75 seconds during 1 circuit attempts.
Aug 14 13:48:06 $HOSTNAME Tor[25362]: We tried for 15 seconds to connect to '[scrubbed]' using exit $EXIT at XXX.XXX.XXX.XXX. Retrying on a new circuit.
Aug 14 13:48:34 $HOSTNAME Tor[25362]: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Aug 14 13:48:53 $HOSTNAME Tor[25362]: Tor has not observed any network activity for the past 62 seconds. Disabling circuit build timeout recording.
Aug 14 13:48:55 $HOSTNAME Tor[25362]: Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 64 seconds during 1 circuit attempts.
Aug 14 13:48:58 $HOSTNAME Tor[25362]: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Just want to see if anybody else can help figure something out, I'm hesitant to file a bug report as I have yet to see anywhere online of someone having the same issues.

Post Reply