Open rootzoll opened 3 years ago
Both that project and https://en.wikipedia.org/wiki/Tor2web appear to be 'a bit dated'. There is not much activity on the issues and PRs.
need more in depth management (better tor connection)
What do you mean by that? :-)
Besides being limited to HTTP (which socat is not) these project still appear to be using the normal TOR client running on a node. So I don't see how they would not have the same (potential) issues as we have seen.
What IP2Tor could do is this: instead of selling a bridge port on only one server, it could sell the same port on 2 or 3 (or more) servers in a single order. Then you would have 2 or 3 IP:Port combinations that point to the same HS. If you then create a DNS A record that resolves (round Robin?!) to alle 2 or 3 IPs you would have some resiliency/load sharing.
Maybe if the single tor-forwarding bridges need more in depth management (better tor connection) it can help to take a look at this project that reaches a similar goal for serving single websites: https://github.com/DonnchaC/oniongateway