Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #29487

Closed (moved)
(moved)
Open
Created Feb 13, 2019 by Trac@tracbot

SOCKS5 handshake fail when client sending user/pass auth method

After updating Tor to 0.3.5.7 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.

Trac:
Username: access_denied

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking