[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24977 [Core Tor/Tor]: Non-fatal assertion !(tor_mem_is_zero((const char*)node->hsdir_index->fetch, DIGEST256_LEN))
#24977: Non-fatal assertion !(tor_mem_is_zero((const
char*)node->hsdir_index->fetch, DIGEST256_LEN))
-------------------------------------------------+-------------------------
Reporter: asn | Owner: dgoulet
Type: defect | Status:
| accepted
Priority: Medium | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.2.1-alpha
Severity: Normal | Resolution:
Keywords: tor-hs, prop224, | Actual Points:
034-triage-20180328, 034-removed-20180502 |
Parent ID: | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by asn):
Thanks for the logs cypherpunks from comment:8. Do you have info logs by
any chance? That would be really useful.
Seems like we just triggered the debugging code we added in #25306. See:
{{{
should_rotate_descriptors(): Bug: Service descriptor is NULL
((nil)/(nil)). Next rotation time is 1526367600 (now: 1526378468). Valid
after time from consensus is 1526378400 (on Tor 0.3.3.5-rc )
}}}
Pretty fun that we end up with both descriptors as NULL.
This seems like not-so-hard to reproduce by starting up an HS with a hella
skewed clock, and then setting it up to the right time so that it gets the
right consensus.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24977#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs