Next-Generation onion services (v3) support #69
Comments
Linking from a Reddit discussion:
|
See https://trac.torproject.org/projects/tor/ticket/26768 for the respective torproject trac ticket. |
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. |
Linked this from Tor's new community projects page |
There is a new STEM release available: https://stem.torproject.org/change_log.html#version-1-8 |
Any updates on this? Oh man I really need it for v3. |
I'm currently working on this. Please expect a release around March :) |
Please see https://lists.torproject.org/pipermail/tor-dev/2020-January/014142.html for initial testing instructions. |
The alpha testing guide has moved to git: https://github.com/asn-d6/onionbalance/blob/master/docs/alpha-testing-v3.txt |
Quote https://blog.torproject.org/cooking-onions-reclaiming-onionbalance
|
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. |
This has been implemented. Closing. |
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.
The text was updated successfully, but these errors were encountered: