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

Closed (moved)
Open
Opened Jun 03, 2018 by Alexander Færøy@ahf🍍Developer

Fix problems with the Windows event loop

We currently have a number of problems that is due to different issues around the Windows event loop:

  • We do not have bi-directional communication with sub-processes, which limits what we can do with PT's and the upcoming Onion Naming Service sub-process.

  • We should look into whether we dynamically can check if the Windows version that Tor is running on supports UNIX domain sockets such that Tor Browser can do its "network-less sandbox"-feature where it connects to Tor via the UNIX domain sockets. See: https://blogs.msdn.microsoft.com/commandline/2017/12/19/af_unix-comes-to-windows/

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#26295