Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 681
    • Issues 681
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1550

Closed
Open
Opened Apr 25, 2019 by akwizgran@akwizgranOwner
  • Report abuse
  • New issue
Report abuse New issue

Relay encrypted messages between contacts

Several users have suggested that Briar should relay encrypted messages between contacts, so that users who can't communicate directly can pass messages through mutual contacts.

This would have implications for battery and bandwidth consumption. If message propagation was restricted then it would also have privacy implications (Alice could see that Bob and Carol were both sending messages at 3am, when nobody else was sending anything). If message propagation was unrestricted then the battery and bandwidth impact would be hard to control - this would affect scalability and enable flooding attacks. Fair queueing might help to mitigate flooding attacks (#511).

One user suggested that the privacy impact could be mitigated through fine-grained controls (e.g. Bob and Carol would only choose Alice to relay their messages if they didn't mind her knowing when they were communicating). I'm skeptical about whether most people can predict and manage their privacy needs at that granularity in advance, but I could be wrong.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1550