Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torbutton
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • torbutton
  • Issues
  • #40045
Closed
Open
Created Aug 25, 2021 by Matthew Finkel@sysrqbMaintainer

Teach the controller's watchEvent about status_client and how to return raw messages

These are needed by Tor Launcher when it begin using torbutton's controller. Currently, the controller only recognizes stream events, but we need status_client in Tor Launcher. In addition, watchEvent eats the first two keys of the event (the code: 650, and the type: STATUS_CLIENT). We need these in Tor Launcher, too.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking