Skip to content
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.

Next-Generation onion services (v3) support #69

Closed
Alicesland opened this issue Jan 9, 2018 · 12 comments
Closed

Next-Generation onion services (v3) support #69

Alicesland opened this issue Jan 9, 2018 · 12 comments

Comments

@Alicesland
Copy link

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
Copy link
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.

@asn-d6
Copy link
Collaborator

asn-d6 commented Jul 12, 2018

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

@cretz
Copy link

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
Copy link

Linked this from Tor's new community projects page

@duritong
Copy link
Contributor

There is a new STEM release available: https://stem.torproject.org/change_log.html#version-1-8

@afshar-mohammad
Copy link

Any updates on this? Oh man I really need it for v3.

@asn-d6
Copy link
Collaborator

asn-d6 commented Jan 20, 2020

I'm currently working on this. Please expect a release around March :)

@asn-d6
Copy link
Collaborator

asn-d6 commented Feb 2, 2020

Please see https://lists.torproject.org/pipermail/tor-dev/2020-January/014142.html for initial testing instructions.

@asn-d6
Copy link
Collaborator

asn-d6 commented Feb 8, 2020

The alpha testing guide has moved to git: https://github.com/asn-d6/onionbalance/blob/master/docs/alpha-testing-v3.txt

@adrelanos
Copy link

Quote https://blog.torproject.org/cooking-onions-reclaiming-onionbalance

we just added v3 support for Onionbalance

@asn-d6
Copy link
Collaborator

asn-d6 commented Mar 18, 2020

Yes indeed. I'm still waiting for a bit of testing feedback before I replace the actual pip/debian packages with the new onionbalance.

So, please, if you test this let me know so that I get more confidence that I haven't broken anything.

@asn-d6
Copy link
Collaborator

asn-d6 commented Apr 8, 2020

This has been implemented. Closing.

@asn-d6 asn-d6 closed this as completed Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants