Repository navigation
spec(port): port the padding block cipher mode uniformity guard (Refs #8884) - #9752
Closed
dmitrii-f-t27 wants to merge 2 commits into
Closed
dmitrii-f-t27 wants to merge 2 commits into
dmitrii-f-t27 wants to merge 2 commits into
Conversation
…HashTag#8884) The twenty-eighth W2 target of the CR-CHAT-04 ring tracker: the ciphertext-uniformity rules - the batch ceiling, then per block the size check, the zero-block probe, the entropy floor, the repeated-hash scan and the repeated-index scan - as the D5 verdict with every payload field, the original's rule order, and all ten PBCU tests transcribed plus helper and rule-order tests. The original's Vec<u8> block data becomes the fixed [16]u8 form plus its length (the bytes stay; the zero probe reads them), and the Shannon entropy arrives as a number the caller computed - the lane convention for statistics over byte buffers, and here a necessity: the t27c gen-rust backend does not yet lower @log (zero-arity .log() call, E0061 under rustc) while the native backend computes it fine. Both BTreeSet dedups become scans. Checks (conventions 0-14): t27b test 12 passed 0 failed; t27c test-report 12/12, 0 vacuous; gen-rust output compiles under rustc; coverage Untested 0; ASCII only; seal saved, all hashes MATCH;
Contributor
Author
|
Merge request for the gHashTag merger: steward READY (required all SUCCESS — validate, check-linked-issue, parse-ratchet, t27b-native-linux, t27b-native-macos; the red ones are non-required per Q16 and red on master too). Ledger row included; one-line rebase if the earlier lane PRs land first — I take it on request. |
This was referenced Oct 17, 2026
This was referenced Oct 17, 2026
Merged
Merged
Merged
…ave2-aa # Conflicts: # docs/reports/t27b_expectations.json
Contributor
Author
|
Superseded by #10175: the remaining CR-CHAT targets now land as one port-wave batch per specs/policy/pr_budget.t27 (#10067/#10074), which asks for one PR per ring batch instead of one per file. The spec body, seal and ledger row in this PR are unchanged there; the batch also carries one self-consistent duplicate-body bless. Closing this one-file PR keeps the merge queue and the Actions queue small. |
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.
Refs #8884 (CR-CHAT-04 ring tracker). Parent epic: gHashTag/trios#1812 (W2, own lane, T-PORT). Twenty-eighth W2 target delivered: the ciphertext-uniformity rules — batch ceiling (4096), per-block size check (16), zero-block probe, entropy floor (3.0 bits/byte), repeated-hash scan ([32]u8) and repeated-index scan (u64) — D5 verdict carrying idx / got / bound / got_f / bound_f for every variant, original rule order, all ten PBCU tests transcribed plus helper and rule-order tests (12 total, 0 vacuous). Vec block data → fixed [16]u8 + its length (the bytes stay; the zero probe reads them); Shannon entropy arrives caller-computed — the lane convention for statistics over byte buffers, and here a necessity: the t27c gen-rust backend does not yet lower @log (zero-arity .log() call, E0061 under rustc) while native t27b computes it fine (probed; documented). Both BTreeSet dedups → visited-scans. Fixture blocks' entropies are exact: the original's (i·79+seed) walks give sixteen distinct bytes = 4.0 bits. t27b 12/12 native; t27c 12/12; gen-rust compiles under rustc (0 errors, 0 &'static str, 0 Vec<const); coverage Untested 0; seal all hashes MATCH; ledger row included (pass, non-pass untouched). Dedup checked. Sequencing: one-line ledger rebase if the earlier lane PRs land first — I take it on request.