Argon2 on x86-64: prove complete independent-address generation - #494
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
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.
Generate the complete independent-address block used by Argon2i and Argon2id. Clear the input and zero blocks, write the seven public address words, and call the verified G compression twice to produce exactly
Spec.Argon2.addressBlock.Prove the whole operation from arbitrary initial scratch contents, including memory permissions and separation, frames, callee-saved registers, MXCSR preservation, and equal traces for public frame, stack and scratch pointers. Compose short argument/clear/header proofs with the existing verified compression call boundary; no new contracts or trusted assumptions.
Builds on #490. This remains an inline layer for the forthcoming filling loops. No specification, TCB, public API or generated assembly changes.
Validation: targeted Lean builds of the correctness and trace modules, standard-axiom and compiler-override audits, specification-origin audit, Lean import/proof-speed checks, and
git diff --check. Full checks run in CI.