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

Closed (moved)
Open
Opened Sep 06, 2014 by Lunar@lunar

“Pluggable transport will not be launched” notice makes it hard to read users' logs

Now that pluggable transports are integrated by defaults in the Tor Browser, users' logs contain many times the pluggable transport will not be launched notice:

Pluggable transport proxy (obfs2,obfs3 exec obfsproxy managed) does not provide any needed transports and will not be launched

When no pluggable transports are used, the notice appears 15 times before Tor bootstrap phase begins. Making the log harder to understand than it should.

Maybe the notice ought to be reversed? “Will start pluggable transport X as required”?

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