Skip to content

Release 0.4.14: PqRandom, isolate FIPS, sync AES-GCM, Double Ratchet - #36

Merged
turkananation merged 2 commits into
mainfrom
release/0.4.14
Nov 10, 2026
Merged

turkananation merged 2 commits into
mainfrom
release/0.4.14

Conversation

@turkananation

@turkananation turkananation commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Classical key generation goes through PqRandom / PqBytes.randomBytes (Fortuna is seeded from that hook). Random.secure() remains only the platform default.
  • Background isolates re-enable PqFipsMode and throw if PqRandom.generator is not the platform default. HPKE seal/open refuse every AEAD except AES-256-GCM while the flag is on. AES-128 stays available at the primitive for QUIC Initial. Brainpool, FFDHE, raw PqForgeAeadEngine.seal, and PqXWing itself still do not read the flag.
  • Sync AES-GCM (aesGcm* and AES-128) uses package:cryptography DartAesGcm on little-endian hosts, with the PointyCastle path kept for big-endian. Output is still ciphertext || 16-byte tag.
  • ECDSA P-256/P-384/P-521 share one private curve helper. Public types are unchanged.
  • CLI: global --fips and keygen --pbkdf2-iterations (default 600000). --fips wraps with PBKDF2-HMAC-SHA256 and refuses ChaCha20-Poly1305, Argon2id, X-Wing (hpke keygen|seal|open), and a non-AES-256-GCM HPKE AEAD. Not a validated module.
  • Also ships the previously unreleased 0.4.14 notes: caller-pinned signature policy, profile KEM/signature checks, X.509 anchor selection, and the secure-session nonce salt. No .pqf / .pqfs wire change.
  • Double Ratchet (Signal revision 4, sections 3 and 7.2): DoubleRatchet.initiate / accept / seal / open over X25519 and pqforge AES-256-GCM or ChaCha20-Poly1305. HMAC is pqcrypto (hmacSha256 / hmacSha512). HKDF is RFC 5869 over that HMAC, because pqcrypto does not export HKDF. Header is 40 bytes. Nonce is 12 zero bytes. SHA-512 chain and message keys are the leftmost 32 bytes. MAX_SKIP defaults to 1000. Not libsignal bytes, not PQXDH, not the Sparse Post-Quantum Ratchet, and not a FIPS construction. PqFipsMode refuses the ChaCha suite.
  • Pqxdh and TripleRatchet are exported and throw. XEdDSA is not in this package (Ed25519 is not XEdDSA). The ML-KEM Braid incremental interface is not in pqcrypto. A 1216-byte X-Wing key and an expanded ML-KEM private key are rejected. No .pqf / .pqfs change.

Local checks

  • dart run tool/agent/verify.dart full after the ratchet: 459 passed, 4 skipped
  • Earlier on this branch, before the ratchet commit: CI wrapped-key CLI smoke including --fips, Chrome dart2js sync ChaCha and sync AES-GCM, streaming memory gate (max amplification 0.80x), pinned OpenSSL 4.1.0 and BoringSSL 0.20261020.0, Jaspr pages build, linux-x64 dart compile exe printing pqforge 0.4.14, and CodeQL actions queries with 0 results. Those paths were not re-run for the ratchet commit. The ratchet does not touch interop, the CLI, or .pqf / .pqfs.
  • Visibility regenerated from the manifest. Sync Wiki was not pushed.

Classical key generation reads PqRandom. Background isolates re-enable
PqFipsMode and refuse a custom generator. HPKE seal and open, and the
X-Wing CLI, refuse a non-approved algorithm while the flag is on. Sync
AES-GCM uses the pure-Dart engine on little-endian hosts. pqforge --fips
wraps keygen with PBKDF2-HMAC-SHA256.

Also ships the previously unreleased policy pinning, profile checks,
X.509 anchor selection, and session nonce salt. No .pqf or .pqfs wire
change. This is not a validated module.
Signal revision 4 over X25519 and pqforge AEAD. HMAC comes from pqcrypto.
PQXDH and the Triple Ratchet are fail-closed scaffolds. No .pqf/.pqfs
change. Not libsignal bytes and not a validated module.
@turkananation turkananation changed the title Release 0.4.14: PqRandom, isolate FIPS, sync AES-GCM Release 0.4.14: PqRandom, isolate FIPS, sync AES-GCM, Double Ratchet Nov 10, 2026
@turkananation
turkananation merged commit 3ac14e2 into main Nov 10, 2026
12 checks passed
@turkananation turkananation self-assigned this Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant