Repository navigation
feat(algo): classical strength by NIST's method (ENH-001 spec and calculator) - #16
Merged
Merged
Conversation
Review of why cipher strength is shown only as an uncited four-word heuristic on the TLS report and PDF, and nowhere else (CLI, Inventory, SSH, groups, keys, API, CBOM); single DES is rated Weak, not Insecure. Proposes one cited model (NIST SP 800-57 Part 1 Rev. 5 Table 2, RFC 9325) in the catalogue and evaluation, shown on every surface, with acceptance tests.
GNFS estimate for RSA and finite-field DH (FIPS 140-3 IG D.B, as stated in SP 800-56B Rev. 2 Appendix D), rounded to the nearest multiple of eight; elliptic curves at half the order's bit length (SP 800-186); symmetric ciphers and hashes from SP 800-57 Part 1 Tables 2 and 3. Tests reproduce SP 800-56B Table 4, SP 800-56A Table 26 and SP 800-186 Table 1 exactly. ENH-001 gains the derivation and worked examples.
khalid-offset
changed the title
khalid-offset
changed the title
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 review and enhancement spec for "why is strength not shown for the detected ciphers?": ENH-001. It now includes §5, how NIST calculates strength, reproduced.
Calculator (
internal/algo/strength.go)The tests reproduce SP 800-56B Table 4 (2048 → 110.1 → 112 … 8192 → 201.7 → 200), SP 800-56A Table 26 (the ffdhe groups) and SP 800-186 Table 1 exactly.
Not yet wired into the UI, CLI, API or CBOM: that follows owner approval of the spec and OD-1.