Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #11108

Closed (moved)
Open
Opened Mar 01, 2014 by cypherpunks@cypherpunks

SocksPolicy and DirPolicy ignore port specifications, contrary to documentation

The documentation for SocksPolicy and DirPolicy both say "policies have the same form as exit policies", but looking at the code at https://gitweb.torproject.org/tor.git/blob/4348c52a353a5242ddefc5c866ffb58e98443c7e:/src/or/policies.c#l344 it appears both only consider the address, not the port number. The documentation should be updated to reflect this.

(It seems unlikely to me that limiting the source ports allowed to connect to these listeners is actually a feature anyone wants, but maybe it is?)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#11108