25 Mar
2018
25 Mar
'18
12:54 a.m.
Turns out this is a known bug in tor.
s7r reported [1] it several years ago (2014-12-13).
In [1] a log warning has been added, [2] is about the actual fix.
[1] https://trac.torproject.org/projects/tor/ticket/13953 [2] https://trac.torproject.org/projects/tor/ticket/19919
--
https://mastodon.social/@nusenu
twitter: @nusenu_