> for v3 support, HSFETCH won't be ncessary...
N...
HSFETCH
is an absolutely necessary control function now critical to operation of a
variety of onionland search / index / status / webhosting / research services,
and any other basic commandline checks that have zero wish to be
spawning
> On 30 Apr 2018, at 23:55, David Goulet wrote:
>
>> On 28 Apr (09:34:09), teor wrote:
>>
>> On 28 Apr 2018, at 04:48, Damian Johnson wrote:
>>
OnionBalance requires STEM support for V3
>>>
>>> Hi Alec, would you mind clarifying what you
On 28 Apr (09:34:09), teor wrote:
>
> On 28 Apr 2018, at 04:48, Damian Johnson wrote:
>
> >> OnionBalance requires STEM support for V3
> >
> > Hi Alec, would you mind clarifying what you need from Stem? As far as
> > I'm aware Stem supports v3 onion service creation...
>
Hi nusenu,
I've just finished catching up with this thread, ticket changes,
and the IRC discussion overnight.
> On 28 Apr 2018, at 09:30, teor wrote:
>
> On 28 Apr 2018, at 05:56, nusenu wrote:
>
>>> And also we will be able to reduce the
>>>
On 28 Apr 2018, at 04:48, Damian Johnson wrote:
>> OnionBalance requires STEM support for V3
>
> Hi Alec, would you mind clarifying what you need from Stem? As far as
> I'm aware Stem supports v3 onion service creation...
>
>
On Fri, Apr 27, 2018 at 04:03:00PM -0400, grarpamp wrote:
> a) If defined as shifting v3 to be "provisioned by default" via docs
> and function, while *continuing to support v2* functionality
> on the network, there's no problem, everyone is happy.
> b) While v2 and v3 do share some capabilities,
> Yes indeed. The sooner we deprecate v2 the sooner we can stop worrying
> about malicious HSDirs.
yes, that was indeed the motivation for my email (mostly because I see how much
time
goes into the constant detection and rejection of these relays - not by me)
> And also we will be able to
On 27 April 2018 at 19:48, Damian Johnson wrote:
> > OnionBalance requires STEM support for V3
>
> Hi Alec, would you mind clarifying what you need from Stem? As far as
> I'm aware Stem supports v3 onion service creation...
> ...
> I'm unaware of the ball being in my court
On Fri, Apr 27, 2018 at 8:01 AM, Alec Muffett wrote:
> OnionBalance
Forgot to include this in the former list of
common / useful onion tools, thanks.
If anyone knows of others, feel free to add to thread.
> OTOH, I have been performance testing simultaneous
> OnionBalance requires STEM support for V3
Hi Alec, would you mind clarifying what you need from Stem? As far as
I'm aware Stem supports v3 onion service creation...
https://trac.torproject.org/projects/tor/ticket/25124
See the 'version 3' note at the end of...
Jonathan Marquardt writes:
> On Wed, Apr 25, 2018 at 04:58:36PM -0400, grarpamp wrote:
>> In onionland, there seems to be little knowledge of v3, thus little worry
>> about v2 in cases where v3 would actually apply to benefit, that's bad.
>
> v3 onion services just seem like a
It's not just about getting the protocol stack right, but also the
ancillary software environment; people keep asking me for "V3 support in
EOTK" and my stock response is this:
BEGIN
OnionBalance requires STEM support for V3, before it can be updated
(possibly a substantial rewrite will
On Wed, Apr 25, 2018 at 04:58:36PM -0400, grarpamp wrote:
> In onionland, there seems to be little knowledge of v3, thus little worry
> about v2 in cases where v3 would actually apply to benefit, that's bad.
v3 onion services just seem like a way worse deal to the average user and
the
nusenu writes:
> Hi,
>
> even though you are probably years away from deprecating onion v2 services
> it is certainly good to have a clear plan.
>
> I'm asking because the sooner onion v2 are deprecated the sooner some
> people can stop worrying about malicious HSDirs.
Hi nusenu, thanks for bringing this up! Filed tickets for a couple
things we should sort out before deprecating v2...
https://trac.torproject.org/projects/tor/ticket/25918
https://trac.torproject.org/projects/tor/ticket/25920
___
tor-dev mailing list
On Wed, Apr 25, 2018 at 2:22 PM, nusenu wrote:
> even though you are probably years away from deprecating onion v2 services
> it is certainly good to have a clear plan.
>
> I'm asking because the sooner onion v2 are deprecated the sooner some
> people can stop worrying
16 matches
Mail list logo