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
  • #1160

Closed (moved)
Open
Opened Dec 02, 2009 by Trac@tracbot

AllowSingleHopExits setting can be bypassed by client

Using the software Tortunnel http://www.thoughtcrime.org/software/tortunnel/ it is easy to setup a 1-hop proxy through a selected exit node, even if the node has AllowSingleHopExits set to 0 (default).

Maybe i'm being alarmist, but this seems like abuse waiting to happen - a disaster for exit node operators and for network capacity re:p2p. If this isnt fixable in a few days i'll be switching to non-exit.

[Automatically added by flyspray2trac: Operating System: All]

Trac:
Username: keb

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