[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2490: anonymous friendly tahoe create-node/create-client

Tahoe-LAFS trac at tahoe-lafs.org
Fri Sep 4 02:58:15 UTC 2015


#2490: anonymous friendly tahoe create-node/create-client
-------------------------+-------------------------------
     Reporter:  dawuud   |      Owner:  daira
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.10.1
   Resolution:           |   Keywords:  tor i2p anonymous
Launchpad Bug:           |
-------------------------+-------------------------------

Comment (by str4d):

 `--listen` and `--location` docs should be at the top of the list if they
 are required (since the list has no defined ordering at present). They
 should probably be above the `Options` section to emphasize this, although
 that would likely require more backend changes to the config flag handling
 code.

 I agree with [https://github.com/david415/tahoe-
 lafs/commit/a360fea767e5db2a0c76d5c19f77b18ec8ca4b00 daira's comments on
 the commit] - the distinction between the two arguments is unclear.
 Examples for each would help, as well as something to clarify the
 difference between them, or connecting them to the corresponding
 `tahoe.cfg` variables. Again, maybe a section above "Options" would help.
 (This is stepping into man-page territory though.) Alternatively, maybe
 `--location` could be renamed `--advertize` (or `--broadcast` for
 something with consistent spelling) to better convey its meaning.

 [https://tahoe-lafs.org/pipermail/tahoe-dev/2015-August/009569.html
 warner's email] mentioned additional arguments like `--tor-only` and
 `--listen-on-tor`. As I say in ticket:517#comment:33, I don't think these
 scale. Additionally, they duplicate information from `--listen`:

 * `--tor-only` is equivalent to `--listen=tor:foo`.
 * `--listen-on-tor` is equivalent to `--listen=tcp:0,tor:foo` (or
 `--listen=tcp:0 --listen=tor:foo`, it's unclear which will be used).

 If `--listen` is to be required and will be the authoritative source of
 what-to-listen-on information, then additional arguments for configuring
 the type of setup are IMHO unnecessary.

 For arguments specific to configuring Tor/I2P/etc, I think `--tor-*`,
 `--i2p-*` etc. make the most sense. For clients, they can easily be
 collected and passed straight to the plugins; for servers, the relevant
 server code can just use them directly. I can't think of any arguments
 that a user might want to pass to both Tor and I2P.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2490#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list