Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #30125
Closed
Open
Created Apr 11, 2019 by David Fifield@dcfOwner

Port server's log sanitization to client, broker, and proxy-go

legacy/trac#21304 (moved) added a log sanitizer to the server (bridge) code that searches for IP addresses in logs and elides them. We noted in comment:17:ticket:21304 that the other components--client, broker, and proxy-go--can benefit from the same log sanitization.

comment:18:ticket:21304 suggests a way to do it: move the logScrubber code into a new top-level subdirectory and safelog package, and have the other programs import git.torproject.org/pluggable-transports/snowflake.git/safelog.

Assignee
Assign to
Time tracking