Repository navigation
Release 0.4.14: PqRandom, isolate FIPS, sync AES-GCM, Double Ratchet - #36
Merged
Merged
Conversation
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.
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.
Summary
PqRandom/PqBytes.randomBytes(Fortuna is seeded from that hook).Random.secure()remains only the platform default.PqFipsModeand throw ifPqRandom.generatoris 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, rawPqForgeAeadEngine.seal, andPqXWingitself still do not read the flag.aesGcm*and AES-128) usespackage:cryptographyDartAesGcmon little-endian hosts, with the PointyCastle path kept for big-endian. Output is still ciphertext || 16-byte tag.--fipsandkeygen --pbkdf2-iterations(default 600000).--fipswraps 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..pqf/.pqfswire change.DoubleRatchet.initiate/accept/seal/openover 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_SKIPdefaults to 1000. Not libsignal bytes, not PQXDH, not the Sparse Post-Quantum Ratchet, and not a FIPS construction.PqFipsModerefuses the ChaCha suite.PqxdhandTripleRatchetare 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/.pqfschange.Local checks
dart run tool/agent/verify.dart fullafter the ratchet: 459 passed, 4 skipped--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-x64dart compile exeprintingpqforge 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.