pqforge

pqforge

Post-quantum application crypto for Dart and Flutter. HPKE, envelopes, certificates, and a CLI, on pqcrypto.

pqforge is the application layer on pqcrypto. The primitives stay there. This package is what you call when a program has to seal a record, sign a release, wrap a key, mint a certificate, or run HPKE.

0.4.13 makes `PqRsa.verifyPkcs1` and `verifyPss` accept a 1024-bit modulus, adds `PqRsaHash.sha1` and `PqRsaHash.sha224`, and adds `PqEd448` (RFC 8032, empty context for DNSSEC algorithm 16). Generation stays 2048, 3072, or 4096. 0.4.12 adds `PqBrainpool` and `PqFfdhe`: the three brainpool TLS groups and the five RFC 7919 finite-field groups. Agreement only. Not a TLS stack, and not constant-time. 0.4.11 adds `PqBytes.sha1` (RFC 3174). Collision resistance is broken. It is there for a standard that still names SHA-1, such as DNSSEC NSEC3. It is not a signature. 0.4.10 adds RFC 9180 HPKE. 0.4.9 is X.509 and the classical signatures those certificates use. 0.4.8 is the ChaCha20 keystream. None of those changed the `.pqf` or `.pqfs` wire format. Not a FIPS 140 module.
import 'package:pqforge/pqforge.dart';

That import is pure Dart. No dart:ffi on the path, so the same library runs on the Dart VM, Flutter, and the web. File streaming that needs dart:io is package:pqforge/pqforge_io.dart.

What landed and was easy to miss#

ReleaseYou can call
0.4.13 PqRsa verifies 1024, 2048, 3072, and 4096 bit moduli. PqRsaHash.sha1 and PqRsaHash.sha224 . PqEd448 for RFC 8032 and DNSSEC algorithm 16.
0.4.12 PqBrainpool and PqFfdhe . brainpoolP256r1, P384r1, P512r1, and ffdhe2048 through ffdhe8192.
0.4.11 PqBytes.sha1 and sha1OfStream. RFC 3174, 20 bytes. Not for a new protocol.
0.4.10 PqHpke — base, PSK, auth, authPSK. X25519, X448, P-256, P-384, P-521. AES-GCM and ChaCha20-Poly1305.
0.4.10 Signature legs. slhDsa: on detached recipes. compose-sign for a dual or a triple. Opt-in ECDSA-P384 and ECDSA-P521. See Signatures .
0.4.9 PqX509 , PqEcdsaP384 , PqRsa , PqEd25519 , and pqforge cert .
0.4.8 PqSymmetricPrimitives.chacha20 — RFC 8439 keystream, including a QUIC header-protection mask.

The rest of the package is unchanged in role: ML-KEM envelopes, ML-DSA and SLH-DSA detached signatures, hybrid sessions, multi-recipient envelopes, Argon2id key custody, and the CLI. The pages below are the map. The claim boundary is the list of sentences this package is allowed to say.

PageWhat it covers
Agreement PqBrainpool, PqFfdhe, NIST ECDH, X25519, X448, and the combiner.
Envelopes Profiles, .pqf, .pqfs, multi-recipient, hybrid KEM-DEM.
KeysKeygen, Argon2id, PBKDF2, custody stores.
HPKERFC 9180. Four modes, five KEMs.
CertificatesX.509 and PKCS#10.
Symmetric AES-GCM, ChaCha20-Poly1305, the keystream, sessions.
BytesSHA-1, SHA-2, HMAC, length prefixes.
ClassicalEd25519, ECDSA, RSA, and the hybrid signers.
SignaturesDetached, hybrid-sign, compose-sign.
RecipesBindings, logs, tokens, artifacts.
CLIEvery command.

The same 0.4.10 release also widens signatures. That does not change the HPKE row above. Signatures has the new legs: slhDsa: on the detached recipes, compose-sign for a dual or a triple, and opt-in ECDSA-P384 / ECDSA-P521. P-521 ECDH on the Classical page is still the HPKE share, not that signature.

Agreement · Envelopes · Keys · HPKE · CLI · Claim boundary