From meskio at sindominio.net Mon Jun 15 21:06:01 2020 From: meskio at sindominio.net (meskio) Date: Mon, 15 Jun 2020 21:06:01 +0200 Subject: [onionmx] SRV and v3 onions In-Reply-To: <154513498371.18868.8116932479813716466@localhost> References: <154513498371.18868.8116932479813716466@localhost> Message-ID: <159224796126.3310.17361884844863723592@localhost> I bump this thread because tor seems to have already a timeline of deprecation of onion services v2: https://lists.torproject.org/pipermail/tor-dev/2020-June/014365.html Basically we have 15 months to migrate to v3. I believe all the reasons that kept me publishing the v2 in the SRV record at the time of this thread are not valid anymore. And is time to use onion v3 in onionmx. Quoting meskio (2018-12-18 13:09:43) > In sindominio we have added a v3 onion to our onionmx setup. And now I'm > wondering what to do with our _onion-mx._tcp. SRV record. > > I'm tempted to put the v3 there. But seeing that the tor version in debian > stable doesn't have support for v3 onions, I'm wondering how many things are > going to break by that. (the one in stretch-backports does support v3) > > Is anybody publishing v3 onions in their SRV? > Are we assuming people uses up to date tor? > Should we keep the v2 in our record until most distros get a more modern version > of tor? > Is it worth to consider how to publish more than one record? -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: signature URL: