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

Closed (moved)
Open
Opened Sep 30, 2015 by Isis Lovecruft@isis

Don't print bridge IPs/fingerprints in WARN/NOTICE log messages

By default, we currently print out bridge IP:ports and fingerprints in tor's log messages at the notice and warn levels. Users often copy+paste these logs to various public places when trying to debug why their connection isn't working.

I understand that this is probably useful information to give to the support desk for debugging why tor isn't working… but would it be doable to have the support people ask, "Hey could you add SafeLogging 0 to your torrc?" or something?

I think the default should be to sanitise bridge IP:ports and fingerprints at these levels.

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