Opened 2 years ago
Closed 2 years ago
#22736 closed defect (fixed)
prop224: Update spec wrt overlap behavior of HSes
| Reported by: | asn | Owned by: | asn |
|---|---|---|---|
| Priority: | Medium | Milestone: | Tor: 0.3.2.x-final |
| Component: | Core Tor/Tor | Version: | |
| Severity: | Normal | Keywords: | prop224, tor-hs |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | 1 | |
| Reviewer: | Sponsor: | SponsorR-can |
Description
Teor asked a few questions wrt HS overlap logic and we started digging into the implementation to see if it conforms to the spec:
https://lists.torproject.org/pipermail/tor-dev/2017-June/012336.html
It seems like the code does not do the 36 hour expiration logic, and instead it generates HSDir indices for all nodes upon receiving a new consensus.
We should verify that the logic in the code makes sense and has no problems, and then update the spec to specify the right behavior.
Child Tickets
Change History (3)
comment:1 Changed 2 years ago by
| Owner: | set to asn |
|---|---|
| Status: | new → assigned |
comment:2 Changed 2 years ago by
| Parent ID: | #21888 |
|---|
comment:3 Changed 2 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has been fixed many times and finally merged with 0b290856ba3d0823e0f5b56ed7628a2352d38324 in tor-spec.git and upstream has exactly that.
Note: See
TracTickets for help on using
tickets.
Also, this is not prop224 groundwork.