Anonymity Development Roadmap

Development phases

Phase 1. Use Tor for network connectivity and to protect identity of client

note: Client side is endpoint agnostic and server side has TCP endpoint support only.

Dependencies

txsocksx: get this merged upstream -->> https://github.com/david415/txsocksx/tree/endpoint_parsers_retry_socks - client Twisted endpoint for Tor
Foolscap trac ticket 203: switch to using Twisted Endpoints
Tahoe-LAFS trac ticket 1010: anonymous client mode
Tahoe-LAFS trac ticket 517: make tahoe Tor- and I2P-friendly

Phase 2. Use I2p for network connectivity and to protect identity of client

Dependencies

Tahoe-LAFS trac ticket regarding client endpoint string parameter concatenation
txi2p

Phase 3. endpoint-agnostic Foolscap server side

Completing these two tickets will make Foolscap endpoint agnostic on the server side. Therefore any Twisted server endpoint/parser can be used with Foolscap

Teach twisted to serialize a listeningPort into a client endpoint descriptor - https://twistedmatrix.com/trac/ticket/7603
open new foolscap ticket - Add getClientEndpoint() to use the feature from twisted trac ticket 7603

Phase 4. Integrated Tor Hidden Service feature for storage servers

teach tor to create Hidden Service directories with group rx perms https://trac.torproject.org/projects/tor/ticket/11291
open new txtorcon ticket - Teach endpoint to use control port feature from tor trac ticket 11291

2.1 KiB Raw Blame History