You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of #1. I'm taking ChaCha20 (the stream cipher, RFC 8439 block function; the init(key, nonce) / update / reset_nonce API from #1) on every target listed in the README, one architecture at a time:
PPC64le: contract → implementation (no PPC64le model upstream yet)
Each item is its own PR (or PRs), following the one-kind-of-change-per-PR rule. This claim is for ChaCha20 itself, not the ISA models for x86 / ARM64 / ARMv7 / PPC64le: if someone else lands one of those first I'll build on it, and I'll comment here before starting one myself. ChaCha20-Poly1305 is not part of this claim.
Part of #1. I'm taking ChaCha20 (the stream cipher, RFC 8439 block function; the
init(key, nonce)/update/reset_nonceAPI from #1) on every target listed in the README, one architecture at a time:Spec/ChaCha20.lean(transcribed from RFC 8439 §2.1–2.4) and the x86-64 contract of its block function — Spec: ChaCha20 (RFC 8439) and the x86-64 contract of its block function #13 (merged)rolby k isrorby 32−k, so no further TCB additions) — ChaCha20 on x86-64: verified block function and the ChaCha20 API #18 (merged)Each item is its own PR (or PRs), following the one-kind-of-change-per-PR rule. This claim is for ChaCha20 itself, not the ISA models for x86 / ARM64 / ARMv7 / PPC64le: if someone else lands one of those first I'll build on it, and I'll comment here before starting one myself. ChaCha20-Poly1305 is not part of this claim.