Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M meek
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • meek
  • Issues
  • #29364
Closed
Open
Issue created Feb 07, 2019 by David Fifield@dcfOwner

Tone down [WARN] log messages resulting from meek-client output

Since legacy/trac#28179 (moved), tor logs any output from managed proxies' stderr at the WARN level. So meek-client's log messages like

2019/02/07 08:12:22 listening on 127.0.0.1:39071

that formerly went into a black hole, now get logged by tor as

2/7/19, 08:12:22.657 [WARN] Managed proxy at './TorBrowser/Tor/PluggableTransports/meek-client' reported: 2019/02/07 08:12:22 listening on 127.0.0.1:39071

The only real problem here is one of user interface. Being logged at WARN level causes the ⚠️ to pop up in Tor Launcher, when this is not something that requires user attention at all.

May affect other transports.

Assignee
Assign to
Time tracking