Trace-only segmentation of cipher implementations, no labels or metadata, just repetition-scale estimates and stable cores.
trending10
01 02 A reminder that PQ migration targets asymmetric crypto first, and AES-128/SHA-256 may still be fine despite the 256-bit cargo cult.03 Walsh LUTs on lazy CKKS bits speed up AES transciphering, because apparently XORs deserved a detour.04 Your standard cells can be the Trojan, and this paper scores how hard it is to notice before tapeout.05 Can AEGIS be bitsliced without becoming a crime scene? This paper says yes, with CT ARM, RISC-V, wasm, and JS code.06 Client-side proxy swaps PII for type-matched surrogates, then stitches the originals back, since plain redaction wrecks utility.07 Benchmarks stock OpenSSL 3.5.6 on RISC-V Karu, showing what Zvk/Zvkned buy over plain rv64gc and what OpenSSL still ignores.08 AMD apparently yanks TSME from consumer Ryzen, leaving the ciphertext to PRO and EPYC where it always wanted to be.09 Survey of Rijndael-256, the wider-block AES variant meant to dodge 128-bit birthday limits, with a cryptanalysis roundup.10 SP 800-38D Rev. 1, Second Pre-Draft Call for Comments: GCM and GMAC Block Cipher Modes of Operation csrc.nist.govRijndael-256 is back on the menu, via NIST's comment call on GCM/GMAC revisions and a proposed wGCM variant.