#29660 closed defect (fixed)

TorBrowser > 8.0.2, XMPP - can not connect to socks5 anymore

Reported by: o9491020 Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: TorBrowserTeam201903
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:



I set up my xmpp client to use a SOCKS5 proxy on with ports 9050 or 9150 (see https://riseup.net/en/chat/clients/adium#using-tor) for years is could connect to TOR. This stopped working in any version of the TorBrowser > 8.0.2.

Child Tickets

Change History (3)

comment:1 Changed 15 months ago by arma

This is a result of bug #29175, which is in Tor, and fixed in Tor, but Tor Browser 8.0.x (through x=6) still has the old Tor:

The eventual fix will be to wait for Tor Browser to move to

The workaround in the meantime is to put something (like "x") in your socks username or socks password setting in your xmpp app.

comment:2 Changed 15 months ago by arma

Component: Core TorApplications/Tor Browser
Owner: set to tbb-team
Priority: Very HighMedium
Severity: CriticalNormal

Moving the ticket to Tor Browser component, since the remaining bug is "you're still shipping an old Tor stable".

comment:3 Changed 15 months ago by gk

Keywords: TorBrowserTeam201903 added
Resolution: fixed
Status: newclosed

I bumped the tor version both on maint-8.0 (commit fbd366f2f0a0b1b58642cf5f860d98ba768ebe78) and master (commit 864a167a1cdef48560b52c5f3ba559f343eddae0) for our stable and alpha series. We'll start building with that next week.

Note: See TracTickets for help on using tickets.