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).
This commit is contained in:
Brian Warner
2016-08-28 16:28:01 -07:00
parent bc079a71eb
commit a099b9237d
4 changed files with 37 additions and 32 deletions

View File

@ -39,7 +39,8 @@ install_requires = [
# * foolscap 0.8.0 generates 2048-bit RSA-with-SHA-256 signatures,
# rather than 1024-bit RSA-with-MD5. This also allows us to work
# with a FIPS build of OpenSSL.
"foolscap >= 0.10.1",
# * foolscap >= 0.12.2 provides tcp/tor/i2p connection handlers we need
"foolscap >= 0.12.2",
# Needed for SFTP.
# pycrypto 2.2 doesn't work due to <https://bugs.launchpad.net/pycrypto/+bug/620253>