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

Review Request #1

Closed
whyrusleeping opened this issue Aug 3, 2016 · 1 comment
Closed

Review Request #1

whyrusleeping opened this issue Aug 3, 2016 · 1 comment

Comments

@whyrusleeping
Copy link

The overall approach looks good, and the code looks ok from an "is this good go-ipfs style code?" perspective, but I can't review this technically as I don't have a solid understanding of the TOR addressing scheme, what the addresses signify and the different security implications that doing things a certain way might have.

If you could provide me a short writeup on what Tor multiaddrs for listeners and dialers might look like, and a description of the process of connecting to a Tor service, that would be very helpful.

@david415
Copy link
Owner

david415 commented Aug 3, 2016

here's the tor control port spec:
https://gitweb.torproject.org/torspec.git/tree/control-spec.txt

recently the ephemeral onion service API was added to the control spec. there's an ADD_ONION and DEL_ONION commands. ADD_ONION can optionally specify the onion service private key, otherwise tor will generate a new key. You can also have the tor control port tell you the contents of the new key or not.

currently tor onion address are 80 bits of truncated hash of the public key... in base32 format.

i left a comment here:
libp2p/go-libp2p#79

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