3 Commits

Author	SHA1	Message	Date
Brian Warner	a099b9237d	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).	2016-08-28 16:30:31 -07:00
Brian Warner	bc079a71eb	implement+test I2P setup ... Note that many of the Foolscap handler-creation functions are still stubbed out, so Tahoe won't be able to honor the full range of config syntax until foolscap support is complete.	2016-08-28 03:16:43 -07:00
Brian Warner	15e5ca0e99	exercise TCP/Tor-related tahoe.cfg parsing ... This exercises everything about _make_tcp_handler() and _make_tor_handler() except for when txtorcon cannot be imported.	2016-08-28 03:16:40 -07:00