Changes between Initial Version and Version 1 of Ticket #517, comment 79


Ignore:
Timestamp:
2016-07-06T20:02:14Z (8 years ago)
Author:
warner
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #517, comment 79

    initial v1  
    11Note that this work depends upon a new Foolscap release which provides the socks/tor connection handlers in the right place. [https://foolscap.lothar.com/trac/ticket/242 foolscap#242] and [https://foolscap.lothar.com/trac/ticket/246 foolscap#246] are tracking these.
    22
    3 For the server side, we're still looking at `tahoe create-server --tor` (which is mutually-exclusive with  `--location/--port/--hostname` from #2773), but with enough CLI arguments to let you set these `tahoe.cfg` values right away, because `create-server --tor` will need to use `txtorcon` to spin up a hidden service, extract the private key and onion address, then write both into some as-yet-undefined `tahoe.cfg` fields, where they can be read again at `tahoe run` time to re-create the server endpoint.
     3For the server side, we're still looking at `tahoe create-server --tor` (which is mutually-exclusive with  `--location/--port/--hostname` from #2773), but with enough CLI arguments to let you set these `tahoe.cfg` values right away, because `create-server --tor` will need to use `txtorcon` to spin up a hidden service (using some "file system onion service" class it does/will provide), extract the private key and onion address, then write both into some as-yet-undefined `tahoe.cfg` fields, where they can be read again at `tahoe run` time to re-create the server endpoint.