[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2821: make "tahoe create-client --hide-ip" fail if txtorcon/txi2p are not installed

[Tahoe-LAFS]

#2821: make "tahoe create-client --hide-ip" fail if txtorcon/txi2p are not
installed
--------------------------------+---------------------------
     Reporter:  warner          |      Owner:  warner
         Type:  enhancement     |     Status:  closed
     Priority:  normal          |  Milestone:  1.12.0
    Component:  code-nodeadmin  |    Version:  1.11.0
   Resolution:  fixed           |   Keywords:  anonymity tor
Launchpad Bug:                  |
--------------------------------+---------------------------

Comment (by warner):

 One leftover note: it'd be nice if the outbound-connection-hint-handler
 side of tahoe only relied upon `foolscap[tor]` (or i2p), and didn't look
 for txtorcon/txi2p directly. So, at least in theory, Foolscap could change
 the way it accesses Tor, to use something other than txtorcon, and tahoe's
 outbound side should still work. Of course there's not really much point
 in doing that, since the inbound side (tor_provider) really does need
 txtorcon. Same for I2P.

 So I don't really want to change anything, but just so I remember the idea
 for the future, ideally it'd be nice if create_node either tried to import
 `foolscap.connections.tor` (and caught the failure) to detect when tor was
 unavailable, or delegated the question to some tor_provider method. Maybe
 `TorProvider.is_available()`?

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