Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • emma emma
  • 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
  • emmaemma
  • Issues
  • #7
Closed
Open
Created Mar 03, 2021 by Cecylia Bocovich@cohoshOwner

Capture blocking by "TCP works but SSL gets mangled"

We had a user run emma in Belarus, where they had no access to default bridges, and received results that showed no directory authorities, relays, or bridges were being blocked. This could be because emma only performs a TCP connection and the blocking is happening at the TLS layer.

See censorship-analysis#40002 (closed)

Can we expand these tests to capture this behaviour while still keeping the lightweight design?

Edited Mar 03, 2021 by Roger Dingledine
Assignee
Assign to
Time tracking