Re: Tor Relay log warning
On 5/5/2021 at 5:34 PM, "Theo Buehler" wrote: > >On Wed, May 05, 2021 at 08:06:09AM -0300, Matheus Coelho wrote: >> Hello List! >> >> I have a tor relay server and in version 6.9 of openbsd the log >started >> showing this message: >> >> tor_tls_finish_handshake: Bug: For some reason, wasV2Handshake >didn't get >> set. Fixing that. (on Tor 0.4.5.7 ) Experiencing the same (running a bridge). >> I suspect something related to libressl according to this post: > >Yes, libressl doesn't fully support the info callback that tor >relies on to set wasV2Handshake. This will be a bit tricky to fix. >I think tor will still work, but the log spam is annoying. For what it's worth, metrics.torproject.org now reports my bridge as "offline", so in this instance tor no longer appears to still work. >> https://gitlab.torproject.org/tpo/core/tor/-/issues/40128 > >This post conflates many different issues, most of which should be >resolved. > >> >> it makes sense? >> >> thanks in advance. >> -- >> Matheus Coelho Torres Macedo -lg.
Re: Tor Relay log warning
On Wed, May 05, 2021 at 08:06:09AM -0300, Matheus Coelho wrote: > Hello List! > > I have a tor relay server and in version 6.9 of openbsd the log started > showing this message: > > tor_tls_finish_handshake: Bug: For some reason, wasV2Handshake didn't get > set. Fixing that. (on Tor 0.4.5.7 ) > > I suspect something related to libressl according to this post: Yes, libressl doesn't fully support the info callback that tor relies on to set wasV2Handshake. This will be a bit tricky to fix. I think tor will still work, but the log spam is annoying. > https://gitlab.torproject.org/tpo/core/tor/-/issues/40128 This post conflates many different issues, most of which should be resolved. > > it makes sense? > > thanks in advance. > -- > Matheus Coelho Torres Macedo
Tor Relay log warning
Hello List! I have a tor relay server and in version 6.9 of openbsd the log started showing this message: tor_tls_finish_handshake: Bug: For some reason, wasV2Handshake didn't get set. Fixing that. (on Tor 0.4.5.7 ) I suspect something related to libressl according to this post: https://gitlab.torproject.org/tpo/core/tor/-/issues/40128 it makes sense? thanks in advance. -- Matheus Coelho Torres Macedo
