Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok,|
  040-deferred-20190220, asn-merge   |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-

Comment (by teor):

 Actually, let's get #30051 done, so we do practracker as a pre-push hook.
 Once all the mergers have the pre-push hook, we won't fail CI master any
 more.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok,|
  040-deferred-20190220, asn-merge   |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-

Comment (by teor):

 I pushed an extra commit bffba9d26 to master to accept the following
 practracker change:
 {{{
 -problem function-size
 /src/feature/dirparse/microdesc_parse.c:microdescs_parse_from_string() 154
 +problem function-size
 /src/feature/dirparse/microdesc_parse.c:microdescs_parse_from_string() 169
 }}}

 Let's work out how to solve this merge-forward and practracker fails
 issue.
 Requiring a master merge for each backport is one solution (#29881).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok,|
  040-deferred-20190220, asn-merge   |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by asn):

 * status:  merge_ready => closed
 * resolution:   => fixed


Comment:

 Merged to 040 and onwards.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok,|
  040-deferred-20190220, asn-merge   |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 040-roadmap-proposed, regression?, 035-can, postfreeze-ok,
 040-deferred-20190220
 =>
 040-roadmap-proposed, regression?, 035-can, postfreeze-ok,
 040-deferred-20190220, asn-merge


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 Hexencode isn't very readable, but it's better than nothing.

 Thanks!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * status:  needs_revision => needs_review


Comment:

 I've tried to do the requested changes.  I couldn't log an identifier for
 the MD, since a lot of the code that calls warn_if_nul has no concept of
 individual microdescs, and the code that does have a concept of them
 doesn't know anything about MD identity until after the point when it's
 called.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 CI failed on Windows, it looks like there's some duplicate code, and we
 could log some more useful information about the context of the NUL.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:  .2
 Reviewer:  teor |Sponsor:
-+-
Changes (by asn):

 * reviewer:   => teor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:  .2
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * points:   => .2


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by madage):

 This bug happened on a Linux 32bit machine with self compiled kernel and
 tor. Tor was built without libseccomp/sandbox support. libc is glibc 2.28.

 After nick brought the 41min gap between last-listed relay times to my
 attention, I thought it was related to a power failure that seems to have
 happened at that time. kern.log has a last entry about 9h10 and a reboot
 at 9h48. However, after a close look at tor notice.log, I see that tor
 itself was restarted at 9h10 after not being able to get a rendevous
 descriptor and it finished bootstraping at 9h11. After that tor was
 restarted again at 9h49.

 I should mention that I was not the user who first reported this to teor
 months back, but maybe (s)he had a power failure/tor restart while
 fetching the microdescriptors as well?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by toralf):

 This is a stable hardened Gentoo Linux server.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * actualpoints:   => .2


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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):

 * status:  accepted => needs_review


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 I wonder if any other programs are looking at these files too.  Does arm
 poke them at all?  Is there any other tool in use?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Okay, let's try to figure this out.  The nuls are on line 16158, between
 the end of one md and the start of the annotations for the next.  There is
 a 41-minute gap between the @last-listed times of the two microdescs.

 The NULs fill the file between position 0d8546 and 0xd9000 inclusive.
 That last figure suggests to me that we're maybe doing an improper seek.

 Looking at the code in microdesc.c, if we're doing an improper seek, I
 suspect the following places:
* tor_fd_getpos(), which calls lseek to find the current position in
 the file.  This doesn't seem too likely to me, since it happens between
 writing the annotations and writing the descriptor.
* The call from start_writing_to_file() to tor_fd_seekend().  This
 looks correct to me, alas.
* The call to for_fd_setpos() in microdesc_cache_rebuild().  I have
 trouble believing this call is the cause of the problem, since it happens
 when we're rebuilding the main cache, and this bug is in the journal.

 Now, here is another thought.  Is this happening as we write to disk, or
 at some earlier phase?  That is, this bug would also make sense if we had
 something padding microdesc bodies with nuls before or after we downloaded
 them.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  assigned => accepted


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by madage):

 Attached my cached-microdescriptors file where the bug happened. Yesterday
 the cache must have been rotated as I am not seeing the warnings anymore.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by madage):

 * Attachment "cached-microdescs.new.xz" added.

 cached-microdescriptors file with nul bytes filled relay info

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * owner:  (none) => mikeperry
 * status:  new => assigned


Comment:

 Assigning to Mike to add some logging, because everyone else has been
 assigned more than two 040-must tickets.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-must, 040-roadmap-proposed,  |  Actual Points:
  regression?, 035-can, postfreeze-ok,   |
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:
 040-roadmap-proposed, regression?, 035-can, postfreeze-ok,
 040-deferred-20190220
 =>
 040-must, 040-roadmap-proposed, regression?, 035-can, postfreeze-ok,
 040-deferred-20190220
 * milestone:  Tor: unspecified => Tor: 0.4.0.x-final


Comment:

 A user on IRC reported this bug in 0.4.0.3-alpha.

 We should re-triage this ticket in 0.4.0.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:
  035-can|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  035-roadmap-proposed, regression?, 035-can => 040-roadmap-
 proposed, regression?, 035-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final


Comment:

 This is a ticket for better logging, it can go in 0.4.0.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  035-must, 035-roadmap-proposed,  |  Actual Points:
  regression?|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 "internal nul character" sounds like it's getting junk in its
 microdescriptors, either from a messed up directory source, a messed up
 cache file, maybe a bug in fetching and uncompressing microdescriptors.

 It would be good to improve the log messages here, and maybe we'll get a
 better idea what is happening.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  035-must, 035-roadmap-proposed,  |  Actual Points:
  regression?|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * priority:  Medium => High
 * keywords:  035-roadmap-proposed, regression? => 035-must, 035-roadmap-
 proposed, regression?


Comment:

 We must triage this issue in 0.3.5.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs