Argon2 on x86-64: prove the filling matrix state transition - #497
Closed
reaperhulk wants to merge 1 commit into
Closed
reaperhulk wants to merge 1 commit into
reaperhulk wants to merge 1 commit into
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.
Connect the verified x86-64 filling step to
Spec.Argon2.fillBlock: represent the lane-major assembly allocation as the specification's block array, prove that the step changes exactly the current cell, and prove the complete matrix agrees with the reviewed state transition when supplied its specified random word.Memory initialization establishes the same representation invariant. Each filling step retains the frame values, loop registers, permissions and allocation/separation invariants needed for the following iteration. Add target-independent proof lemmas exposing the reviewed step's random word, array update and permitted-reference log; the specification itself is unchanged.
Builds on #496. Proofs only; no specification, TCB, API or assembly changes. Selecting the random-word source and composing the nested loops follows.
Validation: targeted Lean builds, standard-axiom and compiler-override audits, specification-origin audit, Lean import/proof-speed checks, and
git diff --check. Full checks run in CI.