Security analysis: TMTO reconciliation, validated sims, lower-bound notes - #1
Open
dcondrey wants to merge 2 commits into
Open
Security analysis: TMTO reconciliation, validated sims, lower-bound notes#1dcondrey wants to merge 2 commits into
dcondrey wants to merge 2 commits into
Conversation
Replace the stale/inconsistent TMTO section (three conflicting formulas, inflated 197x-3137x table) with the paper's branching-process Theorem 3 + Temporal Staleness (Thm 4) + Adaptive Bound (Thm 5), and add an empirical Amortization Resistance section. Reconciles all downstream references; renders clean via kramdown-rfc + xml2rfc. NOTE: SECURITY-REVIEW.md flags that the paper's Theorem 3 depth-rho mechanism is empirically inaccurate and needs re-derivation. Signed-off-by: David Condrey <david@writerslogic.com>
…ound notes SECURITY-REVIEW.md: full analysis (lattice framing rejected; TMTO reconciled to the paper; validated pebbling; scaling shows unbounded/scrypt-class memory-hardness and that the paper's depth-rho claim is empirically off by ~4.5x). tmto-*.py: four reproducible simulations; the pebbling engine is validated against ROMix's proven Theta(N^2). POSME-LOWER-BOUND.md: a reduction *draft* (not a proof) toward cc_mem = Theta(K^2/rho), with the metric/log-factor/amortization gaps explicitly flagged unresolved. None of the formal constants are certified; the robust results are empirical. Signed-off-by: David Condrey <david@writerslogic.com>
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.
Reviewed, honest security analysis of PoSME's memory-hardness. Nothing here is a certified result; the formal constants are explicitly not proven. Merge at your discretion.
Draft sync (commit 1): rewrites the draft's stale TMTO section (three conflicting formulas, an inflated 197x-3137x table) to match the published arXiv paper's Theorems 3-5, plus an empirical Amortization Resistance section. Renders clean (kramdown-rfc + xml2rfc).
Analysis + evidence (commit 2):
The empirical findings are trustworthy (validated engine); the formal bound wants a cryptographer. This is the natural artifact to put in front of EKR / a CFRG reviewer.