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

Closed (moved)
Open
Opened Mar 22, 2018 by Arlo Breault@arlo

Broker: investigate non-domain-fronting secure client / proxy registrations

Pasting discussion from email,

in the Flashproxy case, registration wasn't bidi, and I think they imagined using insecure channels to register like OSSes. In Snowflake, the client is making TLS connections with the broker, which amounts to the same thing as encrypting the payload with the facilitator's public key.

Also,

There's also the case where an adversary DOSes the facilitator with a bunch of fake client or proxy registrations and things like that.

This is now #25593 (moved)

Also, there is the potential that in the future we might need some sort of non-domain-fronting rendezvous. It seems that right now we have an ecosystem of tools growing that assumes domain-fronting will always be available & effective. May be worth considering how to prepare for regions where this might not work as well in the future.

So this ticket should probably be for that.

\ Migrated from https://github.com/keroserene/snowflake/issues/13

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