Repository navigation
Accept bounded auth challenges with normal clock skew - #15
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
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 fresh macOS production acceptance rejected challenges before signing, then rapid retries exhausted authentication budgets. Validate the five-minute lifetime against the challenge issue time while keeping the existing 30-second future-issue bound, origin/identity binding, expiry matching and expired-challenge rejection. Add six clock/lifetime boundary regressions. The production harness now honors Retry-After, stops on invalid challenges and retains sanitized initial errors and clock offsets. Typecheck, build and focused tests passed; CI and another live two-machine acceptance remain required.