Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #5551

Closed
Open
Opened Apr 02, 2012 by Karsten Loesing@karsten

Deployed obfsproxy package for both bridge and user side

Item 11 from org/sponsors/SponsorF/Year2 is: "obfsproxy: get a deployed package for both bridge and user side."

AFAICS, we have bundles for the user side, but we're currently not maintaining them. When do we think we'll maintain them again? And is it reasonable to call the first half of this deliverable done once we're maintaining them again, even without finishing Vidalia/BridgeDB/statistics/NAT punching support as written in the pluggable transport deployment roadmap?

Looks like we don't have bundles for the bridge side yet. The pluggable transport deployment roadmap says that "we plan to incorporate obfsproxy in Tor Bridge Bundle." When do we plan to do that? And can we call the second half of this deliverable done once we have a Tor Bridge Bundle with obfsproxy, even without Vidalia/BridgeDB/statistics/NAT punching support?

Cc'ing the people who come to mind when thinking about obfsproxy and bundles. Optimistically assigning to July. Who's going to lead this deliverable?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#5551