Re: [tor-dev] Onion Service v2 Deprecation Timeline

On 15 Jun (12:34:17), David Goulet wrote: > This effectively means that from _today_ (June 11th 2020), the Internet has > around 15 months to migrate from v2 to v3 once and for all. Typo: June 11th 2020 --> June 15th 2020 :) David -- 262Gy/4o+HGG/7ELoDp1drRojN33l7AZaBoRHN6mjXY= signature.asc

Re: [tor-dev] Reproducing #33598 "chutney does not fail on some SOCKS errors"

On Mon, Jun 15, 2020 at 8:53 AM c wrote: > > I asked on ticket https://bugs.torproject.org/33598 how to reliably > reproduce SOCKS errors so that it would be easier to determine when the > underlying issue is properly fixed, rather than running into the > possibility of race conditions (as the cur

Re: [tor-dev] #32888 IPv6 and 'Address' option

On Sun, Jun 14, 2020 at 6:42 AM c wrote: > > Trac describes > that "we should also log [for] IPv4 and IPv6: the Address torrc option" > and as tor(1) states, 'Address' takes only an IPv4 address and port. > > So what is suggested here? Make '

[tor-dev] Onion Service v2 Deprecation Timeline

Greetings everyone! I will try to make this quick. Deprecation of v2 has already been discussed on this list [0] and so this is not about re-creating this discussion but rather giving you the Tor Project timeline for v2 deprecation. To very quickly summarize why we are deprecating, in one word: S

[tor-dev] Reproducing #33598 "chutney does not fail on some SOCKS errors"

I asked on ticket https://bugs.torproject.org/33598 how to reliably reproduce SOCKS errors so that it would be easier to determine when the underlying issue is properly fixed, rather than running into the possibility of race conditions (as the current workaround depends on "waiting long enough" for