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 694
    • Issues 694
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • 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
  • #1416

Closed
Open
Opened Oct 08, 2018 by Torsten Grote@groteOwner

Build pluggable transport binaries for Android

We would focus on obfs4 as it should still work in countries like Iran or China (if the bridge host itself is not blocked via TCP). Also, obfs2 and 3 are obsolete, and scramblesuit has no advantages over obfs4 that we know of.

The first task is to work out whether we need a standalone obfs4 executable or a go library. If we use the library, do we also need the dispatcher so tor can control the transport? Then we'll know whether our upstream is yawning's obfs4 or the shapeshifter-transports library.

There's also Guardian Project's Android Pluggable Transports and OpenPriv's Android Go Mobile Builder that might be relevant.

The extra artifact that gets added to Briar should be reproducible: How to Reproduce Go binaries byte-by-byte

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