#28223: Unparseable microdescriptor on public relay -------------------------------------------------+------------------------- Reporter: teor | Owner: nickm Type: defect | Status: | accepted Priority: Medium | Milestone: Tor: | 0.4.0.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: 040-roadmap-proposed, regression?, | Actual Points: 035-can, postfreeze-ok, 040-deferred-20190220 | Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by nickm):
* keywords: 040-must, 040-roadmap-proposed, regression?, 035-can, postfreeze-ok, 040-deferred-20190220 => 040-roadmap-proposed, regression?, 035-can, postfreeze-ok, 040-deferred-20190220 * priority: High => Medium Comment: I would also love to know what platform this has happening on. I would _guess_ it's a reasonably normal linux, but I haven't heard one way or another. I've written a diagnostic patch as `bug28223_diagnostic_035`; I think we should merge it in 0.4.0 but not backport. It also includes a couple of extra `#include`s, though I bet they won't be needed. There is a PR at https://github.com/torproject/tor/pull/891 . Going to remove this from "040-must" since it is not actually harmful, and does not appear to be new in 040. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28223#comment:14> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs