Opened 21 months ago

Closed 21 months ago

Last modified 21 months ago

#29487 closed defect (duplicate)

SOCKS5 handshake fail when client sending user/pass auth method

Reported by: access_denied Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


After updating Tor to on my Debian system, Proxychains won't connect to Tor via SOCKS5 (SOCKS4 works normally). In handshake, proxychains sents auth methods "no auth" and "user/pass", Tor selects "user/pass", proxychains sents empty username and pass, Tor returns success status, proxychains sents connection request, Tor returns general failure status. If application don't send "user/pass" auth method, Tor selects "no auth" in socks handshake and connection establishes normally.

In log:
Tor[]: socks5: parsing failed - invalid user/pass authentication message.
Tor[]: Fetching socks handshake failed. Closing.

Wireshark log is in attachment.

Sorry for bad English.

Child Tickets

Attachments (1)

pchains-failed.pcapng (2.0 KB) - added by access_denied 21 months ago.

Download all attachments as: .zip

Change History (3)

Changed 21 months ago by access_denied

Attachment: pchains-failed.pcapng added

comment:1 Changed 21 months ago by rl1987

Resolution: duplicate
Status: newclosed

#29175 - fixed and merged to master.

comment:2 Changed 21 months ago by nickm

(also merged to maint-0.3.5)

Note: See TracTickets for help on using tickets.