On 1/4/19, V wrote:
> "crypto" "security" "sofware dev" "support" fud re v2
"Hey, here's v2, it uses older crypto and mechanics that
are not as robust etc as v3... However v2 offers useful features
for many users, and those features are not yet available in a
newer design (volunteers to create
On 1/4/19, teor wrote:
>> Node operators (tor-relays) would continue offering
>> v2 HSDir support module until such time as the reasons
>> for choosing v2 by those above are supported in v3 or vN.
>
> It's not just about feature parity.
Right. Feature parity is nice and excellent goal, till
On 01/04/2019 09:17 AM, s7r wrote:
> Mirimir wrote:
>> On 01/03/2019 11:06 PM, teor wrote:
>>
>>
>>
>>> Hopefully, we'll have feature parity on v3 very soon. And then
>>> apps will migrate from v2 to v3 (or dual-stack).
>>>
>>> It's best if we transition slowly, in a planned manner. But we do
>>>
Mirimir wrote:
> On 01/03/2019 11:06 PM, teor wrote:
>
>
>
>> Hopefully, we'll have feature parity on v3 very soon. And then
>> apps will migrate from v2 to v3 (or dual-stack).
>>
>> It's best if we transition slowly, in a planned manner. But we do
>> need to transition in the next few years.
On 01/03/2019 11:06 PM, teor wrote:
> Hopefully, we'll have feature parity on v3 very soon. And then
> apps will migrate from v2 to v3 (or dual-stack).
>
> It's best if we transition slowly, in a planned manner. But we do
> need to transition in the next few years. Otherwise, we might have
>
> relays have a rather distinct signup and fingerprint pattern
> usually seen for onion attacks.
> ...
> a) If you are an .onion operator I'd like to encourage you to switch to onion
> services version 3
> ...
> so we can start
> ...
> b) dropping onion version 2 services eventually.
These are
