Repository navigation
Reject ambiguous/lossy JSON at every CLI input boundary; release 0.7.2 - #7
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
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.
Scope
Close the Core 0.7 installation audit's CLI input findings. Use one strict parser for inline/file/stdin JSON, reject duplicate members (including escaped aliases), invalid UTF-8/Unicode, non-finite values and unsupported precision-losing integers without rewriting input. Preserve exact large binary64 integers and canonical JCS shortest spellings using rfc8785==0.1.4. Reject repeated --ext keys. Keep explicit legacy endpoints and plaintext create arguments.
Successful HTTP response JSON and outgoing values use the same boundary. No claim that parsing verifies signatures, authorization or external truth.
Validation
Added 46 tests spanning malformed and legitimate inputs plus no-network/no-fallback regressions; existing tests retained. Local syntax compilation passed; full dependency-installed test run must pass in hosted CI before merge. Software version 0.7.2, not a new protocol draft. Historical signed bytes and IETF -07 unchanged.