[tor-dev] prop224: What should we do with torrc options?

Yawning Angel yawning at schwanenlied.me
Wed Nov 23 23:37:07 UTC 2016

On Thu, 24 Nov 2016 01:18:46 +0200
s7r <s7r at sky-ip.org> wrote:
> Yes, this looks good to me as well. As for ADD_ONION, I think we
> should give the people that use it automatically for other apps a
> change until they upgrade to be compatible with v3, so for the
> transition period as long as v2 is supported (but not recommended) in
> the network, ADD_ONION controller command will create a v2 service,
> and we add another controller command: ADD_ONIONV3 that will create
> v3 services. When v2 is permanently gone, we make ADD_ONION a synonym
> to ADD_ONIONV3, remove the RSA1024/SHA1 code and we're all set.

What.  Why.  Anyone right now, that explicitly wants a v2 service
going forward, should use `ADD_ONION` correctly.  It takes the type of
key for a reason.


Yawning Angel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20161123/d06fed5c/attachment.sig>

More information about the tor-dev mailing list