Repository navigation
Conversation
… their HMAC variants
bcgit#95 not already on this branch
… and CLI wiring (PR bcgit#89)
… bits in the MSBs, unused low bits ignored
…ke the other hashes
…ptor with multi-block and one-shot methods (PR bcgit#107)
…-free bit-sliced AES permutation (PR bcgit#105)
…nd aes*-cbc CLI subcommands (PR bcgit#106)
…ryptor/PaddedDecryptor) (PR bcgit#97)
…me lengths, AES_CBC_* aliases, simpler CLI (PR bcgit#109)
…mmands and shared block-mode CLI (PR bcgit#111)
…locks8, SymmetricCipherEncryptor/Decryptor (from feature/sm4); CFB follows suit
…cb CLI subcommands; block-mode CLI generic over INIT_DATA_LEN
…S_PADS; SymmetricCipherEncryptor::do_final reports its output length
…with API changes and per-commit summaries
…rams/HashMLDSAParams/MLKEMParams traits, one impl per parameter set (bcgit#117)
…eamCipherDecryptor pair, shaped like the block cipher pair (in place, any length, generated init data); TestFrameworkStreamCipher implemented in place of its todo!()
… and Cfb8 (SP 800-38A Sec 6.3, s = 8) is added, with AES_CFB8_* aliases, aes*-cfb8 CLI subcommands and a shared stream-mode CLI
…, CFB8 is added, and the StreamCipher trait is replaced by the split encryptor/decryptor pair; re-measured throughput and mutation figures
…inst real AES at all three key lengths, not only the toy permutation
…th picks the counter width (max 4 bytes) and which errors rather than repeat a counter, with AES_CTR_* aliases and aes*-ctr CLI subcommands
… the nonce-plus-counter construction, pinning the 1, 2 and 3-byte counter widths that the ACVP and OpenSSL vectors cannot reach
… their HMAC variants
bcgit#95 not already on this branch
… and CLI wiring (PR bcgit#89)
…es of the ct [u8]
…eing held in a Polynomial [i32; 256], it's now bit-packed into a [u8; 32].
…LVM lays out stack frames and give slightly better numbers
…nd sig on the heap, thus under-reporting
…pansion so that it doesn't get sucked into the caller's stack frame.
…ill memory-hygiene-in-rust.
…skill The Architecture paragraph introducing memory hygiene already names the skill; the stand-alone sentence under Stack Usage Benchmarks repeated it. Also "cast" -> "cost" in that paragraph. Assisted-by: Claude:claude-fable-5-1 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
dghgit
force-pushed
the
mikeo/lowmem_bench_tweaks
branch
from
September 29, 2026 07:51
367fc40 to
681ead7
Compare
dghgit
changed the base branch from
release/0.1.3alpha
to
feature/simple-ciphers
September 29, 2026 07:52
ounsworth
changed the base branch from
feature/simple-ciphers
to
release/0.1.3alpha
October 24, 2026 15:08
Contributor
Author
|
Closing, as this has been replaced by #177 |
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.
In short, I had Claude do a review for silent copies in the mlkem and mldsa lowmemory crates and it found a couple of instance of:
And similar patterns.
The net result is about a 2 - 4 kb reduction across the whole lowmemory suite, and also some tightening up in the non-optimized implementation.