Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #13129

Closed (moved)
(moved)
Open
Created Sep 11, 2014 by Roger Dingledine@arma

Option for downgrading "Rejecting SOCKS request for anonymous connection to private address" log

Tor Browser (or more precisely, both Tor Button and Tor Launcher) intentionally make requests via Tor to 127.0.0.1, because of #10682 (closed). See e.g. https://gitweb.torproject.org/tor-launcher.git/blob/HEAD:/src/install.rdf#l12

So we have a thin but steady stream of users who see

Rejecting SOCKS request for anonymous connection to private address [scrubbed]

warnings in their logs, and ask us what the deal is.

That said, in other situations I've actually found it useful for that warn to show up, since e.g. my Pidgin was making requests to 127.0.0.1 rather than to the xmpp server, and that was a bug in my Pidgin.

Does that argue for a torrc option that TB can set to indicate that it knows it'll be doing this otherwise-considered-broken behavior?

Hm.

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