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

non-clearnet peers #5

Closed
cirocosta opened this issue Apr 24, 2021 · 3 comments
Closed

non-clearnet peers #5

cirocosta opened this issue Apr 24, 2021 · 3 comments

Comments

@cirocosta
Copy link
Owner

cirocosta commented Apr 24, 2021

  • setup tor proxy
  • figure out i2p? never used it
  • setup a full node in both
  • figure out go support for socks proxy (I guess that's how we could make what we have "just work"?)

uuh, this is sick: https://github.com/ipsn/go-libtor
w/ regards to proxy'in, yeah, sounds very simple indeed: https://gist.github.com/Yawning/bac58e08a05fc378a8cc

@cirocosta
Copy link
Owner Author

cirocosta commented Apr 24, 2021

rpc requests just need HTTP_PROXY=socks5://..., so, nothing to be done there (see golang/go@36f55a8)
for levin: 0ffd1c5

@cirocosta
Copy link
Owner Author

8fdd71f socks5 support for crawl

@cirocosta
Copy link
Owner Author

it's working like a charm :) with https://github.com/cirocosta/monero-operator one can bring up a tor-enabled deployment and then point at it (don't even need to run tor locally if you don't want, just port-forward the socks5 proxy port):

kind: MoneroNodeSet
apiVersion: utxo.com.br/v1alpha1
metadata:
  name: node
spec:
  tor:
    enabled: true

then port-forward

k port-forward node-0 9050:9050

and start the crawl

monero crawl --ip=o63olejgzuulvluk7mddyue4l4bxw6k4sdg6kzou7zf2ypgsse3nt2id.onion --port=18083 -x=127.0.0.1:9050

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

1 participant