[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2813: allow tor socks.port= to use unix-domain sockets

[Tahoe-LAFS]

#2813: allow tor socks.port= to use unix-domain sockets
------------------------------+---------------------------
     Reporter:  warner        |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  soon
    Component:  code-network  |    Version:  1.11.0
   Resolution:                |   Keywords:  anonymity tor
Launchpad Bug:                |
------------------------------+---------------------------

Comment (by Brian Warner <warner@…>):

 In [changeset:"a099b9237df462c40c20c48a6240bd1f20573d5e/trunk"
 a099b92/trunk]:
 {{{
 #!CommitTicketReference repository="trunk"
 revision="a099b9237df462c40c20c48a6240bd1f20573d5e"
 tor: socks.port is now a (restricted) endpoint string

 Foolscap has limitations that prevent us from accepting anything but a
 TCP endpoint, but that will change in the future, so make the tahoe.cfg
 syntax accept an endpoint, but then reject non-TCP ones. See the ticket
 for details: refs ticket:2813.

 This depends upon the new `foolscap.connections.tor.socks_port(host,
 port)` API in foolscap-0.12.2, so it bumps the dependency to that (the
 previous commit depended upon 0.12.1, but I hadn't gotten around to
 updating the dep before now).
 }}}

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