Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Background: A similar project #20

Open
rootzoll opened this issue Sep 4, 2020 · 2 comments
Open

Background: A similar project #20

rootzoll opened this issue Sep 4, 2020 · 2 comments

Comments

@rootzoll
Copy link

rootzoll commented Sep 4, 2020

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

@frennkie
Copy link
Owner

frennkie commented Sep 5, 2020

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.

@frennkie
Copy link
Owner

frennkie commented Sep 5, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants