https://trac.torproject.org/projects/tor/wiki/doc/NextGenOnions
Apparently v2 and v3 of onion services can be set up side by side easily (?) enough. Would be nice to see this on the Whonix server in the coming months.
v3 benefits:
- Better crypto (replaced SHA1/DH/RSA1024 with SHA3/ed25519/curve25519)
- Improved directory protocol, leaking much less information to directory servers.
- Improved directory protocol, with smaller surface for targeted attacks.
- Better onion address security against impersonation.
- More extensible introduction/rendezvous protocol.
- A cleaner and more modular codebase.
(And who doesn’t want to manually enter a 56 character long onion address by hand into the url bar? )
Tor trac tickets seem to suggest this could improve occasional issues where .onions are unreachable.
Of course this requires Tor v 0.3.2.1-alpha or later to work (both server and Tor Browser client).
With relevant Tor binaries likely to be available this month for budding testers (3.2.9), it would be nice to actually connect to the Whonix .onion in this configuration. See:
https://blog.torproject.org/tor-0329-released-we-have-new-stable-series
Rise up and some others already support this e.g. here is Rise Up’s v3 .onion ->
http://vww6ybal4bd7szmgncyruucpgfkqahzddi37ktceo3ah7ngmcopnpyyd.onion
Is there anything preventing fortasse from setting this up once relevant binaries are made available via the Tor Project?