Repository navigation
The threat model says a clock agreed back past the newest statement is reported - #324
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The compromised net zone's clock line ended at "only when the user agrees". That is the path 3a's read found for hiding withheld releases: a time weeks back, offered every 10 minutes until someone agrees, leaves the clock behind the newest statement, every newer statement is refused as dated ahead of it, and the 30-day report never comes. #320 reports that case (
update.rsclock_behind,update-test.sh's network step: BEHIND-OK and the status grep). The line now says so, naming the two places the suite reads.Docs only.