PT spec changes for better interoperability with other projects
I spoke with the i2p guys today and here are some of their suggestions for the PT spec. These would make it easier for them (and future other projects) to use Tor's PTs.
Major improvements:
- better spec documentation
- less Tor jargon, split Tor-specific information into separate sections (e.g. Tor env vars)
- some guidelines for non-Tor programs to use PTs
- better handling of per-endpoint config params such as pubkeys, instead of current hack via SOCKS auth params
Smaller enhancements, "good to have":
- possibility of letting a single process to act as both a client (outgoing) and server (incoming).
- flashproxy must allow client-specific remote endpoints (already as #10196 (closed))
- don't trust the entire localhost machine to make outgoing connections, e.g. if one users wants to run his own instance. two options here:
- SSL connection with user/pass to the SOCKS transport client
- use unix domain sockets. This also frees up ports, which is extra-useful in PT composition. Doesn't work on windows, though.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information