Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 219
    • Issues 219
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #40397
Closed
Open
Created Dec 10, 2021 by Richard Pospesel@richardOwner

Create a new build target to package tor daemon, pluggable transports and dependencies

To support censorship-circumvention, 3rd party app developers (like briar, onion share, ricochet-refresh, etc) need a way to package tor + pluggable transports with their application. The current solutions of either 'build them yourself using tor-browser-build' or 'extract them from tor-browser releases' is less than ideal (see: https://forum.torproject.net/t/are-there-any-official-reproducible-tor-obfs4proxy-binaries/831/3 ).

We should separately archive and publish the contents of what becomes the 'Tor' directory in tor-browser in a standard place as part of our release process so 3rd parties can easily integrate tor+PTs into their own applications.

@boklm @msimonelli

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