Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M monit-configuration
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • monit-configuration
  • Issues
  • #6
Closed
Open
Created Dec 17, 2020 by Philipp Winter@phwReporter

Add "end-to-end" test that talks to moat

To catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 (closed) early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then try to talk to moat and return with exit code 0 if this succeeded.

The challenge is that we should use the same tor and obfs4proxy version as Tor Browser does. And even then, there is no guarantee that we're catching all possible problems – for example, an issue may be limited to Windows. Still, having a test like this would probably go a long way.

(We discussed this topic in today's anti-censorship meeting).

Assignee
Assign to
Time tracking