Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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
  • #11138
Closed (moved) (moved)
Open
Issue created Mar 05, 2014 by David Goulet@dgoulet🐼

Improve code handling SOCKS connection in tor daemon

After a discussion at the weekly little-t tor meeting on #tor-dev, it appears that the code handling SOCKS4/5 connections is a mess:

15:41 < nickm> sad to say, the SOCKS code is a mess right now.  It'll probably need significant testing and refactoring before we can think about extending it

Considering proposal 229 to extend SOCKS5 for Tor use cases, we should work on improving this code base before anything else.

  1. Tests, tests and moar tests
  2. Refactor
  3. Extend

Related issues: #11134, #9221 (closed)

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