Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #13508
Closed (moved) (moved)
Open
Issue created Oct 21, 2014 by Trac@tracbot

Add messaging protocol that is resistant to traffic analysis

This is a proposal to add a messaging protocol that is resistant to traffic analysis. The protocol would allow a message of reasonable length to be sent to a relay, which would then store the message for a variable period of time before forwarding to the next relay in the circuit. Circuits would be built using the message store-and-forward protocol to send setup messages, including circuits to and from Tor hidden service rendezvous points. The variable delay time could potentially be programmed by the client in the message wrapper.

Clients could take advantage of this protocol (including Tor hidden services) to implement messaging clients that are resistant to traffic analysis, i.e., the variable delay between the time messages are received and sent would make it vastly more difficult to determine the endpoints of a message by observing the packets being sent between a set of relays. This protocol would not be suitable for "realtime" applications such as web browsing and voice or video communication; it would only be suitable for text messages, file transfer and similar non-realtime applications.

Trac:
Username: Alan

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