Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 314
    • Issues 314
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #1751
Closed
Open
Created Jul 29, 2010 by Nick Mathewson@nickm👁Owner

Project: Make it harder to use exits as one-hop proxies

Proposal 163 outlined some ways to detect clients, and later emails elaborated on the issue, clarifying some parts and exposing hopeless muddiness in others.

There's an initial implementation of a variant of the concept in Tor now, under the RefuseUnknownExits configuration option. Unfortunately, turning it on seems to give many positives. We haven't investigated whether they're false positives or just jerks using Tor as a one-hop proxy.

Child Tickets: [[TicketQuery(parent=legacy/trac#1751 (moved))]]

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