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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Jun 28, 2013 by David Fifield@dcf

Don't log IP addresses by default in flashproxy.js

flashproxy.js's debug option is too sharp for casual use. It shows what's going on but also contains IP addresses. In #9164 (closed) was originally posted a log containing lots of IPs.

Add a new query string parameter unsafe_logging to be another obstacle to climb over. Maybe don't document it.

At least these messages need to be scrubbed:

Facilitator: got client:{ host: "X.X.X.X", port: YYYY } relay:{ host: "173.255.221.44", port: 9901 }.
Facilitator: connecting to https://fp-facilitator.org/?r=1&client=X.X.X.X%3AYYYY&client=X.X.X.X%3AYYYY
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#9170