Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #9815
Closed
Open
Created Sep 24, 2013 by Philipp Winter@phw

Pluggable transports should learn Tor's data directory

At least ScrambleSuit needs to store persistent information and Tor's data directory would be the best place to do that. Right now, however, pluggable transports have no way of learning the data directory.

A possible fix for that is in the branch pass_datadir (which itself is a branch of bug8979_draft) in: https://github.com/NullHypothesis/obfsproxy

The patches pass the state location (Tor's data directory in managed mode) to the pluggable transport's constructor. For external mode, the patch adds another command line argument to pyobfsproxy.py which allows the user to do that manually.

On the plus side, it's an easy fix. On the minus side, it requires changing existing transports (even though it's just the constructor's method head). An alternative would be yet another method, transports would have to implement?

Please let me know if the patches make sense and if I missed anything. I could restructure it if you don't like the constructor way. Either way, it worked in my tests.

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