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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #3613

Closed
Open
Opened Jul 19, 2011 by Zack Weinberg@zwol

obfsproxy: groundwork for new protocols

Please review and pull from https://github.com/zackw/obfsproxy/compare/master...more-protocols (you will probably find it easier to read individual changes in the series). The branch is called "more-protocols", but I haven't started writing new protocols yet; highlights of what you get are:

  • cleaner protocol-specific API
  • better way to define protocol vtables
  • imported the Tor container library
  • consistent use of "infallible" memory allocation
  • many of the unit tests have been improved
  • fixed some nasty memory leaks in obfs2 and minor ones elsewhere

I plan to keep hacking on this branch; the last commit I'm asking for review of at this time is https://github.com/zackw/obfsproxy/commit/2dd47ce6624d374932f7c212b1f719ad09143c5e (but nothing more is likely to show up till this evening).

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#3613