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

Closed
Open
Opened Dec 17, 2013 by Mike Perry@mikeperry

Can requests to 127.0.0.1 be used to fingerprint the browser?

If a site makes connection attempts or element loads sourced for 127.0.0.1, can it build a list of open local TCP ports for fingerprinting purposes? Open ports may yield different error conditions than closed ports for certain request types and elements..

There may be other vectors to to this through DNS rebinding too, but I believe in those cases the hostname should always be provided to the SOCKS port, and such connections will happen to the exit, which should block them.

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