Skip to content
GitLab
  • Menu
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
  • #10419
Closed
Open
Created 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
Time tracking