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 695
    • Issues 695
    • 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
  • #123

Closed
Open
Opened Dec 02, 2015 by akwizgran@akwizgranOwner

Encrypted crash reports submitted via Tor

If the user chooses to report a crash, the crash reporter should encrypt the crash report with the developers' public key and store it on the disk until the app is re-launched. The app should import the encrypted report, post it to a crash report channel and delete it from the disk.

Messages in the crash report channel should be synced with contacts, but no further. We'll need to add a special contact that's only reachable via Tor for delivering reports to the developers. To prevent the special contact from being a single point where Briar users can be enumerated, it should only be contacted when there are crash reports to deliver.

Users should be able to opt out of sending crash reports and opt out of delivering crash reports for their contacts.

Assignee
Assign to
Milestone C
Milestone
Milestone C (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#123