Changes between Version 1 and Version 2 of Ticket #517, comment 20


Ignore:
Timestamp:
2014-07-01T20:21:00Z (10 years ago)
Author:
dawuud
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #517, comment 20

    v1 v2  
    11
    2 i'm gradually flushing out a rough draft of tor_only mode here:
     2I've made lots of progress in the past few months.
     3
     4Meejah and I released the new Tor Hidden Service endpoint and parser:
     5https://github.com/meejah/txtorcon
     6
     7The Tor client endpoint is also in a working state:
     8https://github.com/david415/txsocksx
     9
     10I have written a 100% backwards compatible fork of Foolscap which uses
     11Twisted endpoint descriptor strings for both the client and server
     12side:
     13https://github.com/david415/foolscap/tree/endpoint_descriptors_server-rewrite6
     14
     15My original Tahoe-LAFS "Tor only mode" feature is here:
    316https://github.com/david415/tahoe-lafs/tree/ticket517
    417
    5 these rough draft changes i made convert all connection hints received from introducer announcements to tor client endpoint descriptors... i tested it with my previously
    6 mentioned twisted endpoints branch of foolscap; it works! or at least
    7 some basic client functionality works...
     18However my second rough draft is higher quality:
     19https://github.com/david415/tahoe-lafs/tree/david-truckee
    820
    9 only_tor should be an option added to tahoe.cfg... but i have not done
    10 that yet...
     21I have tried out this branch of Tahoe-LAFS and found it functional for
     22the client side... The server side has not yet been tested and I
     23believe there to be an issue:
    1124
    12 also i should probably first make all the unit tests pass
    13 again... before adding features.
     25Foolscap needs to become even more endpoint agnostic... in order for the server side of
     26Tahoe-LAFS to use Tor with the txtorcon endpoint... but to do this Twisted needs a
     27new plugin system to serialize IListeningPort objects into endpoint
     28descriptor strings. I will soon attempt to either discuss this on the
     29Twisted mailing list or open a Twisted trac ticket.
    1430
    15 i did not yet try to run an introducer or storage node behind a tor
    16 hidden service using the twisted endpoints foolscap port... in theory
    17 it should just work... unless there are some more incompatibilities with
    18 the endpoints-foolscap location hints format.
    19