[tor-dev] onion v2 deprecation plan?

Jonathan Marquardt mail at parckwart.de
Fri Apr 27 21:14:04 UTC 2018

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, since v2 and v3
> do offer their own exclusive subset of capabilities to users
> that cannot currently be found in the opposing version,
> *removing v2 support* is a definite issue.

I think that, before making v3 the default, all features from v2 like 
HidServAuth should be implemented and should have been around for a couple of 
Tor versions.

Also, what would happen to an old Tor instance with v2 onion services 
configured after the upgrade? These onion services should definitely not 
automatically be switched to v3, as it could break many configurations on 
systems with automatic software updates. I suggest that, if Tor sees an onion 
service configured in torrc and if there's no "HiddenServiceVersion 3" in 
torrc and there are v2 keys in the HiddenServiceDir, it should continue to 
serve a v2 service.

But leaving a note in the log about v3 services if there's a v2 configured 
could be a good thing, I think.

> v3 is a nice advancement and is needed by lots of users
> for what it can do for them, just as v2 is.

Totally agreed.
OpenPGP Key: 47BC7DE83D462E8BED18AA861224DBD299A4F5F3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20180427/f67f6c7b/attachment-0001.sig>

More information about the tor-dev mailing list