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

Next-Generation onion services (v3) support #69

Open
Alicesland opened this Issue Jan 9, 2018 · 4 comments

Comments

Projects
None yet
5 participants
@Alicesland

Alicesland commented Jan 9, 2018

Now that we have a stable release of the 0.3.2 branch next-generation (v3) onion services are hitting the mainstream! onionbalance, in it's current design, does not support v3 onion services.

Being that v3 onion services are the future, it makes sense that onionbalance should work on supporting them.

I'm not sure if you guys allow bounties on this git but it's very important personally that onionbalance supports v3 onion services. I'm willing to provide a reward ($1000+), payed in cryptocurrency, for the brave soul who submits a pull request accomplishing just that.

@alecmuffett

This comment has been minimized.

Show comment
Hide comment
@alecmuffett

alecmuffett Mar 6, 2018

Contributor

Linking from a Reddit discussion:

https://www.reddit.com/r/TOR/comments/82ep61/how_can_i_keep_my_onion_v3_private_publuic_keys/dvabdfm/

OnionBalance requires STEM support for V3, before it can be updated (possibly a substantial rewrite will be needed) to support the new format onions. It's not only a matter of "longer addresses" but also a matter of cross-signing the descriptors to support new-style cryptography, so in fact it might be safest to create a new, separate OnionBalance for V3.

So: STEM needs updating and testing for V3, and then OnionBalance needs to support the new STEM library and encryption. Then (for me) EOTK needs to support the new OnionBalance.

I am not expecting a solution to ship until 2019, earliest.

Contributor

alecmuffett commented Mar 6, 2018

Linking from a Reddit discussion:

https://www.reddit.com/r/TOR/comments/82ep61/how_can_i_keep_my_onion_v3_private_publuic_keys/dvabdfm/

OnionBalance requires STEM support for V3, before it can be updated (possibly a substantial rewrite will be needed) to support the new format onions. It's not only a matter of "longer addresses" but also a matter of cross-signing the descriptors to support new-style cryptography, so in fact it might be safest to create a new, separate OnionBalance for V3.

So: STEM needs updating and testing for V3, and then OnionBalance needs to support the new STEM library and encryption. Then (for me) EOTK needs to support the new OnionBalance.

I am not expecting a solution to ship until 2019, earliest.

@asn-d6

This comment has been minimized.

Show comment
Hide comment
@asn-d6

asn-d6 Jul 12, 2018

See https://trac.torproject.org/projects/tor/ticket/26768 for the respective torproject trac ticket.

asn-d6 commented Jul 12, 2018

See https://trac.torproject.org/projects/tor/ticket/26768 for the respective torproject trac ticket.

@cretz

This comment has been minimized.

Show comment
Hide comment
@cretz

cretz Jul 12, 2018

There was discussion on the mailing list about this, see https://lists.torproject.org/pipermail/tor-dev/2018-April/013128.html. https://trac.torproject.org/projects/tor/ticket/25417 is the ticket to watch.

Also shameless plug, if a "substantial rewrite is needed" and you want to switch languages to something like Go, I wrote https://github.com/cretz/bine which has a goal of feature parity with Stem.

cretz commented Jul 12, 2018

There was discussion on the mailing list about this, see https://lists.torproject.org/pipermail/tor-dev/2018-April/013128.html. https://trac.torproject.org/projects/tor/ticket/25417 is the ticket to watch.

Also shameless plug, if a "substantial rewrite is needed" and you want to switch languages to something like Go, I wrote https://github.com/cretz/bine which has a goal of feature parity with Stem.

@traumschule

This comment has been minimized.

Show comment
Hide comment
@traumschule

traumschule commented Sep 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment