Repository navigation
Expand file tree
/
Copy pathindex.html
More file actions
351 lines (325 loc) · 71.6 KB
/
Copy pathindex.html
File metadata and controls
351 lines (325 loc) · 71.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>pqforge: Post-Quantum Application Recipes for Dart</title>
<meta name="description" content="pqforge turns the pqcrypto ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) primitives into application-ready cryptography: KEM-DEM envelopes, RFC 9180 HPKE, X-Wing (draft-connolly-cfrg-xwing-kem-11, not a .pqf algorithm), AES-256-GCM and ChaCha20-Poly1305 AEAD, an RFC 8439 ChaCha20 keystream, X25519/X448/Ed25519/Ed448/ECDSA-P256/ECDSA-P384/ECDSA-P521/RSA hybrids and signatures, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, X.509 certificates and PKCS#10 requests that OpenSSL req reads, bounded-memory gigabyte streaming, multi-recipient envelopes, Argon2id-wrapped key custody, named recipes, and a universal CLI. SLH-DSA is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign is an opt-in 2-leg or 3-leg signature. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. The core is pure Dart and web-safe — no dart:ffi.">
<meta name="keywords" content="Dart post-quantum encryption, Flutter post-quantum encryption, ML-KEM file encryption, ML-DSA signatures, PQC CLI, post-quantum webhooks, post-quantum document signing, Serverpod PQC, hybrid key agreement, Argon2id key wrapping, RFC 9180 HPKE, ChaCha20 keystream QUIC, X.509 Dart, ECDSA P-384, post-quantum streaming encryption, multi-recipient encryption, FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA, quantum-safe Dart, hybrid signatures Ed25519 ECDSA, pqcrypto composition layer, web-safe Dart encryption, harvest-now-decrypt-later defense">
<meta name="author" content="Turkana Nation">
<meta name="theme-color" content="#07111d">
<link rel="canonical" href="https://turkananation.github.io/pqforge/">
<link rel="icon" href="favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="styles.css">
<meta property="og:type" content="website">
<meta property="og:site_name" content="pqforge">
<meta property="og:title" content="pqforge: Post-Quantum Application Recipes for Dart">
<meta property="og:description" content="pqforge turns the pqcrypto ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) primitives into application-ready cryptography: KEM-DEM envelopes, RFC 9180 HPKE, X-Wing (draft-connolly-cfrg-xwing-kem-11, not a .pqf algorithm), AES-256-GCM and ChaCha20-Poly1305 AEAD, an RFC 8439 ChaCha20 keystream, X25519/X448/Ed25519/Ed448/ECDSA-P256/ECDSA-P384/ECDSA-P521/RSA hybrids and signatures, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, X.509 certificates and PKCS#10 requests that OpenSSL req reads, bounded-memory gigabyte streaming, multi-recipient envelopes, Argon2id-wrapped key custody, named recipes, and a universal CLI. SLH-DSA is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign is an opt-in 2-leg or 3-leg signature. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. The core is pure Dart and web-safe — no dart:ffi.">
<meta property="og:url" content="https://turkananation.github.io/pqforge/">
<meta property="og:image" content="https://turkananation.github.io/pqforge/assets/pqforge-protocol.png">
<meta property="og:image:alt" content="pqforge recipe pipeline from payloads to post-quantum envelopes">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="pqforge: Post-Quantum Application Recipes for Dart">
<meta name="twitter:description" content="pqforge turns the pqcrypto ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) primitives into application-ready cryptography: KEM-DEM envelopes, RFC 9180 HPKE, X-Wing (draft-connolly-cfrg-xwing-kem-11, not a .pqf algorithm), AES-256-GCM and ChaCha20-Poly1305 AEAD, an RFC 8439 ChaCha20 keystream, X25519/X448/Ed25519/Ed448/ECDSA-P256/ECDSA-P384/ECDSA-P521/RSA hybrids and signatures, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, X.509 certificates and PKCS#10 requests that OpenSSL req reads, bounded-memory gigabyte streaming, multi-recipient envelopes, Argon2id-wrapped key custody, named recipes, and a universal CLI. SLH-DSA is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign is an opt-in 2-leg or 3-leg signature. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. The core is pure Dart and web-safe — no dart:ffi.">
<meta name="twitter:image" content="https://turkananation.github.io/pqforge/assets/pqforge-protocol.png">
<script type="application/ld+json">{"@context":"https://schema.org","@type":"SoftwareSourceCode","name":"pqforge","alternateName":"pqforge: Post-Quantum Application Recipes for Dart","description":"pqforge turns the pqcrypto ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) primitives into application-ready cryptography: KEM-DEM envelopes, RFC 9180 HPKE, X-Wing (draft-connolly-cfrg-xwing-kem-11, not a .pqf algorithm), AES-256-GCM and ChaCha20-Poly1305 AEAD, an RFC 8439 ChaCha20 keystream, X25519/X448/Ed25519/Ed448/ECDSA-P256/ECDSA-P384/ECDSA-P521/RSA hybrids and signatures, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, X.509 certificates and PKCS#10 requests that OpenSSL req reads, bounded-memory gigabyte streaming, multi-recipient envelopes, Argon2id-wrapped key custody, named recipes, and a universal CLI. SLH-DSA is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign is an opt-in 2-leg or 3-leg signature. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. The core is pure Dart and web-safe — no dart:ffi.","url":"https://turkananation.github.io/pqforge/","codeRepository":"https://github.com/turkananation/pqforge","programmingLanguage":"Dart","runtimePlatform":["Dart VM","Flutter","Serverpod","CLI"],"license":"MIT","softwareVersion":"0.4.14","applicationCategory":"Cryptography composition library","keywords":["Dart post-quantum encryption","Flutter post-quantum encryption","ML-KEM file encryption","ML-DSA signatures","PQC CLI","post-quantum webhooks","post-quantum document signing","Serverpod PQC","hybrid key agreement","Argon2id key wrapping","RFC 9180 HPKE","ChaCha20 keystream QUIC","X.509 Dart","ECDSA P-384","post-quantum streaming encryption","multi-recipient encryption","FIPS 203 ML-KEM","FIPS 204 ML-DSA","FIPS 205 SLH-DSA","quantum-safe Dart","hybrid signatures Ed25519 ECDSA","pqcrypto composition layer","web-safe Dart encryption","harvest-now-decrypt-later defense"],"maintainer":{"@type":"Person","name":"Turkana Nation"},"publisher":{"@type":"Organization","name":"Yardenah PQ","url":"https://yardenah.com"},"sameAs":["https://yardenah.com","https://github.com/turkananation/pqforge","https://pub.dev/packages/pqforge","https://pub.dev/documentation/pqforge/latest/","https://github.com/turkananation/pqforge/wiki"],"isBasedOn":{"@type":"SoftwareSourceCode","name":"pqcrypto","description":"pqcrypto is the primitives package: pure-Dart NIST FIPS 203 ML-KEM, FIPS 204 ML-DSA, and FIPS 205 SLH-DSA (all 12 parameter sets), plus SHA-2 and SHA-3/SHAKE, with zero runtime dependencies. It exposes raw key generation, encapsulation/decapsulation, and sign/verify over byte arrays.","url":"https://pub.dev/packages/pqcrypto","codeRepository":"https://github.com/turkananation/pqcrypto"},"capabilities":["ML-KEM-512/768/1024 KEM-DEM envelopes through pqcrypto (FIPS 203-aligned)","ML-DSA-44/65/87 detached and pre-hash signatures through pqcrypto (FIPS 204-aligned)","SLH-DSA (FIPS 205, all 12 parameter sets) composed into keygen, custody, and detached sign/verify; not used for envelopes or hybrid-sign. compose-sign can take one SLH-DSA leg when that key is passed","AES-256-GCM and ChaCha20-Poly1305 AEAD on a pure-Dart (PointyCastle) or native (package:cryptography) engine","RFC 8439 ChaCha20 keystream (PqSymmetricPrimitives.chacha20) for a QUIC header-protection mask. Not an AEAD","RFC 9180 HPKE (PqHpke): base, PSK, auth, and authPSK. KEMs DHKEM X25519, X448, P-256, P-384, and P-521. KDFs HKDF-SHA256, SHA384, and SHA512. AEADs AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305, and export-only. BoringSSL 0.20261020.0 interop is base and auth, X25519 and P-256, HKDF-SHA256/384, and the three AEADs. OpenSSL 3.5.9 OSSL_HPKE interop is all four modes, X448 and P-521, HKDF-SHA256/512, and the three AEADs. Not a BoringSSL claim for X448 or P-521. Not an OpenSSL claim for X25519, P-256, or P-384. X-Wing (HpkeKem.xWing, 0x647A, draft-connolly-cfrg-xwing-kem-11) is an additional base and PSK KEM. Auth is rejected. Not a FIPS construction. Not a .pqf or .pqfs algorithm. No BoringSSL or OpenSSL evidence for 0x647A","Signal Double Ratchet revision 4 (DoubleRatchet) over X25519 and pqforge AES-256-GCM or ChaCha20-Poly1305. The header is 40 bytes and the nonce is 12 zero bytes. HMAC is pqcrypto. Not libsignal bytes, not PQXDH, not the Sparse Post-Quantum Ratchet, and not a FIPS module. PqFipsMode refuses the ChaCha suite. Pqxdh and TripleRatchet are exported and throw","X.509 certificates and PKCS#10 requests (PqX509) that openssl req reads: parse, mint, one signature check, and a path check against caller anchors. cert req, cert issue, cert sign, cert inspect, and cert verify. Not a trust store, not AIA, OCSP fetching, or CT","ECDSA P-384 (PqEcdsaP384, low-S), ECDSA P-521 (PqEcdsaP521, low-S; not the HPKE share and not a TLS group), RSA PKCS#1 v1.5 and RSASSA-PSS (PqRsa, SHA-256/384/512), and synchronous RFC 8032 Ed25519 (PqEd25519) and Ed448 (PqEd448, empty context; not an X.509 algorithm)","Bounded-memory .pqfs streaming for gigabyte-scale files: signed header plus independently authenticated frames, auto-engaged at 8 MiB","Multi-recipient envelopes: one sealed payload, the DEM key wrapped per recipient, with no wire-format change","X25519 plus ML-KEM hybrid KEM-DEM so confidentiality holds while either Module-LWE or Curve25519 stands","NIST P-256 and P-384 ECDH (uncompressed SEC1, x-coordinate secret) for TLS hybrid groups. P-521 ECDH is the HPKE share, not a TLS group and not a signature","RFC 5869 HKDF-Extract/Expand (SHA-256 and SHA-384), SHA-384/SHA-512 digest facades, and dart2js-safe sync ChaCha20-Poly1305 with a caller-supplied nonce (`supportsChaCha20Poly1305`)","RFC 3174 SHA-1 (PqBytes.sha1 and sha1OfStream, 20 bytes). Collision resistance is broken. It exists for a standard that still names SHA-1, such as DNSSEC NSEC3 (RFC 5155) and DS digest type 1 (RFC 4034). Not a signature. Not a hash for a new protocol. SHA-256, SHA-384, and SHA-512 remain the digests for new work","ML-DSA plus Ed25519 or ECDSA-P256 hybrid signatures, and standalone ECDSA-P256 (RFC 6979, low-S). hybrid-sign also accepts opt-in ECDSA-P384 and ECDSA-P521. compose-sign opts in 2 or 3 legs among ML-DSA, SLH-DSA, Ed25519, and those ECDSA curves. ECDSA-P384 and ECDSA-P521 are keygen opt-ins, not the default classical set. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group","Digest-mode signing over a streamed SHA-256 for gigabyte artifacts in O(1) memory","pack/unpack a whole folder into one encrypted streaming archive (one KEM encapsulation and one signature for the tree)","Argon2id plus AES-256-GCM wrapped key custody with pluggable stores; PBKDF2 wrapping under FIPS mode","Named recipes for files, folders, text, media, email, documents, webhooks, tokens, records, logs, artifacts, and identity bindings","Universal CLI plus AOT-compiled release binaries for local, server, and release-pipeline workflows; encrypt/decrypt/text/media/folder/pack/unpack/sign/verify/hybrid-sign/compose-sign/ecdsa-sign report live progress (folder jobs forward byte progress from isolates; keygen reports wrapping progress), --quiet mutes per-file lines (and keygen listings), and non-regular files are skipped","FIPS deployment layer (PqFipsMode), swappable lattice backend (PqLatticeProvider), and a swappable DRBG (PqRandom.generator)","Pure-Dart, web-safe core (no dart:ffi); dart:io file streaming behind package:pqforge/pqforge_io.dart"],"doesNotProvide":["CMVP/FIPS 140 module validation","A hard constant-time guarantee for Dart runtimes","A hard memory-erasure guarantee","Public-key trust, identity vetting, or legal e-signature policy","Replay stores, authorization policy, TLS, or secure infrastructure operations","RC4 or unauthenticated encryption","BoringSSL HPKE for X448, P-521, PSK, or HKDF-SHA512","An OpenSSL HPKE claim for X25519, P-256, or P-384","X-Wing as a FIPS construction, an authenticated HPKE KEM, a .pqf or .pqfs algorithm, or a BoringSSL or OpenSSL interop claim","PQXDH and the Sparse Post-Quantum Ratchet (exported scaffolds that throw; XEdDSA and the ML-KEM Braid incremental interface are absent). A libsignal byte match or a FIPS-validated Double Ratchet","A WebPKI trust store, AIA, OCSP fetching, or certificate transparency","ECDSA-P521 as a TLS group or as the HPKE P-521 KEM. PqEcdsaP521 only signs","SHA-1 as a signature or as the hash for a new protocol. PqBytes.sha1 is only the RFC 3174 digest"],"evidenceBoundary":{"allowed_claims":["FIPS 203-aligned ML-KEM through pqcrypto.","FIPS 204-aligned ML-DSA through pqcrypto.","FIPS 205-aligned SLH-DSA through pqcrypto. pqforge composes it into keygen, custody, and detached sign/verify. Envelopes and hybrid-sign remain ML-DSA-only. compose-sign can take one SLH-DSA leg when that key is passed.","Application-layer composition helpers for KEM-DEM, AEAD sessions, hybrid key agreement, streaming, multi-recipient envelopes, wrapped key custody, signatures, recipes, X.509, RFC 9180 HPKE, and CLI workflows.","Best-effort zeroization in Dart."],"forbidden_claims":["FIPS validated","FIPS 140 validated","CMVP validated","certified","hard constant-time Dart guarantee","hard memory-erasure guarantee","ML-KEM alone is secure transport","AES signs documents","RC4 is supported"],"summary":"The package provides application composition around pqcrypto evidence. It is not a validated cryptographic module."},"recipes":[{"name":"Local File Vault","surface":"CLI: keygen, encrypt, decrypt","apps":"developer machines, backup jobs, admin laptops, server batch jobs","apis":"encryptFileBytes, decryptFileBytes, encryptAsync, PqEnvelope","caveat":"Use wrapped secret keys and external storage policy."},{"name":"Folder Archive","surface":"CLI: encrypt-folder, decrypt-folder","apps":"case files, release bundles, evidence folders, internal archives","apis":"encryptFolderEntry, decryptFolderEntry","caveat":"Each file is an independent envelope; folder commands run files concurrently via --concurrency."},{"name":"Folder Pack Archive","surface":"CLI: pack, unpack","apps":"many small files, site exports, evidence bundles, dataset shards","apis":"PqForgePackService (package:pqforge/pqforge_io.dart)","caveat":"One KEM encapsulation and one signature for the whole tree; restores path-traversal-safe and streams end to end."},{"name":"Large Files And Media Streaming","surface":"CLI: encrypt / encrypt-media (auto .pqfs at 8 MiB)","apps":"gigabyte media, datasets, disk images, backups, VM snapshots","apis":"PqForgeStreamCipher.encryptFile, decryptStream (package:pqforge/pqforge_io.dart)","caveat":"Streaming I/O lives behind the dart:io entrypoint; the working set is roughly two frames regardless of file size."},{"name":"Multi-Recipient Envelopes","surface":"CLI: repeatable --recipient-public on encrypt commands","apps":"shared vaults, team archives, escrow, break-glass recipients","apis":"encryptAsync, PqMultiRecipient, PqRecipientSpec","caveat":"The payload is sealed once and key-wrapped per recipient; the app still authenticates each recipient public key."},{"name":"Text Snippets","surface":"CLI: encrypt-text, decrypt-text, sign --kind text","apps":"notes, secrets, prompts, policy snippets, short messages","apis":"sealText, openText, signText, verifyText","caveat":"UTF-8 text only; binary data should use file or media recipes."},{"name":"Media Assets","surface":"CLI: encrypt-media, decrypt-media, sign --kind media","apps":"photos, audio, video, PDFs, campaign media, identity images","apis":"sealMedia, openMedia, signMedia, verifyMedia","caveat":"Bind MIME type and media id; classify content before storing."},{"name":"Document Signing","surface":"CLI: sign, verify","apps":"contracts, reports, certificates, approvals, policy documents","apis":"signDocument, verifyDocument","caveat":"Detached sign may be ML-DSA or SLH-DSA. Application owns legal policy and signer identity vetting."},{"name":"Hybrid And Classical Signatures","surface":"CLI: hybrid-sign, hybrid-verify, compose-sign, compose-verify, ecdsa-sign, ecdsa-verify, cert req, cert issue, cert sign","apps":"release artifacts, firmware, long-lived approvals, dual-trust signing","apis":"PqForgeHybridSigner, PqForgeSignatureComposer, PqEcdsaP256, PqEcdsaP384, PqEcdsaP521, PqEd25519, PqEd448, PqRsa, PqX509, dualSign, dualVerify","caveat":"hybrid-sign policy is require-both or accept-either. compose-sign policy is require-all (default) or accept-any. --digest signs the streamed SHA-256 for gigabyte inputs. ECDSA-P384 and ECDSA-P521 are keygen opt-ins. PqEcdsaP521 is not the HPKE share."},{"name":"Webhook Integrity","surface":"CLI: sign --kind webhook, verify","apps":"payment callbacks, audit delivery, server-to-server events","apis":"signWebhook, verifyWebhook","caveat":"Signer may be ML-DSA or SLH-DSA. Application owns replay windows and key publication."},{"name":"Signed Tokens","surface":"library","apps":"API capabilities, admin actions, short-lived grants","apis":"issueToken, verifyToken","caveat":"Signer may be ML-DSA or SLH-DSA. Application owns revocation and authorization policy."},{"name":"Private Email Payloads","surface":"library","apps":"encrypted mail bodies, secure notifications, outbound archive mail","apis":"sealEmail, openEmail","caveat":"Transport headers and metadata may remain visible unless the app hides them."},{"name":"Government And Medical Records","surface":"library","apps":"public-sector records, patient records, registry payloads","apis":"encryptRecord, appendSignedLogEntry","caveat":"Record encryption is ML-KEM. The signed log may be ML-DSA or SLH-DSA. Application owns access control, retention, and audit policy."},{"name":"Software Artifacts","surface":"CLI/library","apps":"release bundles, firmware, packages, configuration rollouts","apis":"signArtifact, verifyArtifact","caveat":"Sign version and target metadata to block rollback replay. The detached signature may be ML-DSA or SLH-DSA. compose-sign is the separate 2-leg or 3-leg container."},{"name":"Hybrid Server Sessions","surface":"core import (package:pqforge/pqforge.dart)","apps":"Serverpod, API services, local agents, backend handshakes","apis":"PqForgeHybridKeyAgreement, PqForgeSecureSession","caveat":"Authenticate public key bundles and design replay/session storage."}],"generatedBy":"Generated by dart run tool/visibility/generate_visibility.dart. Edit tool/visibility/visibility_manifest.json instead.","dateModified":"2026-11-10"}</script>
<script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is pqforge?","acceptedAnswer":{"@type":"Answer","text":"pqforge is a pure-Dart post-quantum application toolkit. It turns the ML-KEM, ML-DSA, and SLH-DSA primitives from pqcrypto into encrypted files, folders, text, media, email payloads, records, signed documents, signed webhooks, signed tokens, release artifacts, tamper-evident logs, identity bindings, hybrid sessions, wrapped key custody, and a universal CLI. SLH-DSA (FIPS 205) is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign can take one SLH-DSA leg when that key is passed."}},{"@type":"Question","name":"How is pqforge different from pqcrypto?","acceptedAnswer":{"@type":"Answer","text":"pqcrypto is the primitives layer: FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA (all 12 parameter sets), SHA-2, and SHA-3/SHAKE with zero runtime dependencies. pqforge is the application layer built on top of it: KEM-DEM envelopes, AES-256-GCM and ChaCha20-Poly1305 AEAD, RFC 9180 HPKE (X25519, X448, P-256, P-384, P-521), X25519/Ed25519/ECDSA-P256 hybrids plus opt-in ECDSA-P384 and ECDSA-P521, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, key custody, streaming, multi-recipient envelopes, named recipes, compose-sign, and a CLI. SLH-DSA is composed into keygen and detached sign/verify, and is not used for envelopes or hybrid-sign. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. Use pqcrypto for raw algorithms; use pqforge to ship a feature."}},{"@type":"Question","name":"Does pqforge compose SLH-DSA?","acceptedAnswer":{"@type":"Answer","text":"Yes, for key generation, custody, and detached signatures. pqcrypto 0.4.4 ships all 12 FIPS 205 SLH-DSA parameter sets. pqforge exposes them as PqSlhDsaAlgorithm / PqSlhDsaPrimitives, emits a profile-matched SHAKE-f key from keygen (compact 128f, balanced 192f, maximum 256f), and accepts those keys on sign/verify (document, text, media, artifact, webhook) and on issueToken, appendSignedLogEntry, and createIdentityBinding via slhDsa:. Envelope headers, streaming signatures, and hybrid-sign remain ML-DSA-only because SLH-DSA signatures are 8-50 KiB and the s sets are slow. compose-sign can take one SLH-DSA leg when you pass that key. That does not put SLH-DSA on an envelope or on hybrid-sign."}},{"@type":"Question","name":"Is pqforge post-quantum / quantum-safe?","acceptedAnswer":{"@type":"Answer","text":"Yes. It uses NIST FIPS 203 ML-KEM for key establishment and FIPS 204 ML-DSA for signatures through pqcrypto, so confidentiality and signatures resist quantum attacks. Hybrid modes add X25519, Ed25519, or ECDSA-P256 so security also holds if a classical break ever lands on the post-quantum scheme."}},{"@type":"Question","name":"Does pqforge work on Flutter and the web?","acceptedAnswer":{"@type":"Answer","text":"Yes. The core import, package:pqforge/pqforge.dart, is pure Dart and web-safe with no dart:ffi, so the same code runs on the Dart VM, Flutter, and the web. Gigabyte-scale dart:io file streaming lives behind package:pqforge/pqforge_io.dart. On Flutter, FlutterCryptography.enable() adds hardware-backed AEAD."}},{"@type":"Question","name":"Can pqforge encrypt gigabyte files without running out of memory?","acceptedAnswer":{"@type":"Answer","text":"Yes. Inputs at or above 8 MiB automatically use the .pqfs streaming container: a signed master header followed by independently authenticated frames, with a working set of roughly two frames regardless of total size. Per-frame sequence and final-flag binding prevent truncation, reordering, duplication, and splicing."}},{"@type":"Question","name":"Can one ciphertext target multiple recipients?","acceptedAnswer":{"@type":"Answer","text":"Yes. Repeat --recipient-public on the encrypt commands (or use PqMultiRecipient in the library). The payload is sealed exactly once and the DEM key is wrapped to each additional recipient as a metadata entry, costing about 1.6 KB and 2 ms per extra recipient instead of a full re-encryption. Entries can individually be hybrid, and it works for both one-shot envelopes and .pqfs streams."}},{"@type":"Question","name":"Which ciphers does pqforge support, and which is fastest?","acceptedAnswer":{"@type":"Answer","text":"AES-256-GCM (default) and ChaCha20-Poly1305, on a pure-Dart PointyCastle engine or the native package:cryptography engine. Where hardware AES is not dispatched, ChaCha20-Poly1305 measures about 30.4 MiB/s versus 11.5 MiB/s for AES-256-GCM (about 2.6x); with hardware AEAD both exceed 1 GB/s. RC4 is rejected."}},{"@type":"Question","name":"What is the difference between the cryptography and pure-dart engines?","acceptedAnswer":{"@type":"Answer","text":"--engine cryptography (the default) uses package:cryptography and is roughly 10x faster than the PointyCastle reference even in pure Dart, and hardware-backed on Flutter. --engine pure-dart uses PointyCastle only. The wire formats are engine-independent, so an envelope sealed by one engine opens on the other."}},{"@type":"Question","name":"Is pqforge FIPS validated?","acceptedAnswer":{"@type":"Answer","text":"No. pqforge composes FIPS 203/204/205-aligned primitives from pqcrypto, but is not a CMVP or FIPS 140 validated cryptographic module. A PqFipsMode deployment layer restricts suites to AES-256-GCM and PBKDF2-HMAC-SHA256 key wrapping (SP 800-132) and allows a swappable DRBG for validated-module deployments."}},{"@type":"Question","name":"Can pqforge sign and verify documents and releases?","acceptedAnswer":{"@type":"Answer","text":"Yes. It provides ML-DSA detached signatures, recipe-bound signatures for documents, text, media, artifacts, tokens, and webhooks, SLH-DSA (FIPS 205) detached signatures via keygen and sign/verify, hybrid ML-DSA + Ed25519/ECDSA-P256 signatures, and standalone ECDSA-P256 (RFC 6979 deterministic nonces, canonical low-S). AES never signs."}},{"@type":"Question","name":"Can I sign a gigabyte artifact without reading it all into memory?","acceptedAnswer":{"@type":"Answer","text":"Yes. hybrid-sign --digest and ecdsa-sign --digest sign the streamed SHA-256 of the input under a domain-separation label, recorded in the signature JSON so the verify commands re-hash automatically. Envelope signatures are likewise computed over a header-plus-payload hash, so signing cost does not scale with payload size."}},{"@type":"Question","name":"Can pqforge bundle a whole folder into one file?","acceptedAnswer":{"@type":"Answer","text":"Yes. pqforge pack collapses a whole folder into one encrypted streaming archive with a single KEM encapsulation and signature for the tree, roughly 100x less ciphertext overhead than per-file envelopes for a thousand small files. pqforge unpack restores it path-traversal-safe, and a failed unpack removes everything it created."}},{"@type":"Question","name":"What does hybrid mean in pqforge?","acceptedAnswer":{"@type":"Answer","text":"Two independent hard problems guard the same secret. Hybrid encryption combines the ML-KEM shared secret with an ephemeral X25519 exchange using the IETF concatenate-then-KDF construction, so confidentiality holds while either Module-LWE or Curve25519 stands. Hybrid signatures pair an ML-DSA signature with an Ed25519 or ECDSA-P256 signature over the same message. That hybrid command also accepts opt-in ECDSA-P384 and ECDSA-P521. compose-sign is separate: 2 or 3 legs you name, among ML-DSA, SLH-DSA, Ed25519, and those ECDSA curves. ECDSA-P384 and ECDSA-P521 are keygen --classical opt-ins, not the default set. PqEcdsaP521 is not a TLS group and not the HPKE share. Library-only NIST P-256/P-384 ECDH (uncompressed SEC1, x-coordinate secret) is exported for TLS hybrid groups; it is not the X25519 initiate/accept handshake and does not overload PqEcdsaP256. PqEcdsaP384 is the P-384 signature, not that shared secret. PqX509 parses, mints, and checks an X.509 certificate, and it writes the PKCS#10 request openssl req verifies. cert req, cert issue, and cert sign are that CLI. It is not a trust store and not TLS."}},{"@type":"Question","name":"Where does the CLI store keys?","acceptedAnswer":{"@type":"Answer","text":"In the directory passed to keygen --out-dir. Public keys are raw JSON. Secret keys are wrapped JSON when a passphrase source is supplied. keygen emits the full hybrid keyset by default: ML-KEM and ML-DSA, a profile-matched SLH-DSA SHAKE-f key, plus X25519, Ed25519, and ECDSA-P256. --no-slh-dsa skips hash-based keys; --slh-dsa selects specific FIPS 205 sets; --slh-dsa-only emits only SLH-DSA."}},{"@type":"Question","name":"Are CLI keys password protected?","acceptedAnswer":{"@type":"Answer","text":"Yes when keygen is run with --passphrase-env, --passphrase-file, or --passphrase. Wrapped secrets use Argon2id for passphrase-to-key derivation and AES-256-GCM for authenticated encryption of the key bytes, with AAD binding the key kind, algorithm, and key id."}},{"@type":"Question","name":"Can I inspect an encrypted file without decrypting it?","acceptedAnswer":{"@type":"Answer","text":"Yes. pqforge inspect describes any .pqf, .pqfs, key, or signature file: format, profile, suite (for example ML-KEM-1024 + X25519 then HKDF-SHA-512 then AES-256-GCM), engine, signature, recipients, and metadata, without needing a secret key."}},{"@type":"Question","name":"Does pqforge provide identity, trust, or replay protection?","acceptedAnswer":{"@type":"Answer","text":"No. pqforge composes cryptographic building blocks. Public-key trust, identity vetting, replay windows, authorization policy, session storage, and TLS remain the application's responsibility. A self-provided public key is not an identity."}},{"@type":"Question","name":"Is the published package pure Dart? Does it use FFI?","acceptedAnswer":{"@type":"Answer","text":"Yes, it is pure Dart with no dart:ffi, so it runs everywhere Dart runs, including the web. The OpenSSL interop harness used in CI to prove byte-compatibility with the system libcrypto is a separate publish_to: none dev package and is never shipped."}},{"@type":"Question","name":"What HPKE does pqforge implement?","acceptedAnswer":{"@type":"Answer","text":"RFC 9180 Hybrid Public Key Encryption as PqHpke. Modes are base, PSK, auth, and authPSK. KEMs are DHKEM(X25519, HKDF-SHA256), DHKEM(X448, HKDF-SHA512), DHKEM(P-256, HKDF-SHA256), DHKEM(P-384, HKDF-SHA384), and DHKEM(P-521, HKDF-SHA512). X-Wing is an additional KEM, HpkeKem.xWing, id 0x647A, from draft-connolly-cfrg-xwing-kem-11. It is not a DHKEM. Base and PSK work. Auth and authPSK throw. It is not a FIPS construction. FIPS mode rejects it at PqHpke and PqForgeHybridKeyAgreement. There is no BoringSSL or OpenSSL evidence for 0x647A. pqforge hpke writes magic XW01, not PQF1. The custom hybrid is unchanged. Key-schedule KDFs are HKDF-SHA256, HKDF-SHA384, and HKDF-SHA512. AEADs are AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305, and export-only. A sender seals, a recipient opens, and export does not use the sequence number. X448 is RFC 7748 on Dart integers and is not a constant-time claim. BoringSSL 0.20261020.0 is checked for base and auth, both directions, on X25519 and P-256, with HKDF-SHA256 and HKDF-SHA384 and the three AEADs. That API has no PSK and no X448 or P-521. OpenSSL 3.5.9 OSSL_HPKE is checked for all four modes, both directions, on X448 and P-521, with HKDF-SHA256 and HKDF-SHA512 and the three AEADs. That is not an OpenSSL claim for X25519, P-256, or P-384. This is not TLS and not a FIPS module. .pqf and .pqfs are unchanged."}},{"@type":"Question","name":"What is the ChaCha20 keystream for?","acceptedAnswer":{"@type":"Answer","text":"PqSymmetricPrimitives.chacha20 is RFC 8439 ChaCha20. It takes a 32-byte key, a 12-byte nonce, a caller-supplied 32-bit block counter, and returns 1 to 4096 keystream bytes. QUIC header protection uses the first 5 bytes. It is the same Dart engine as chacha20Poly1305Encrypt, so it runs on dart2js. It is not an AEAD: the AEAD forces counter 1 and appends a Poly1305 tag."}},{"@type":"Question","name":"Does pqforge read and mint X.509 certificates?","acceptedAnswer":{"@type":"Answer","text":"Yes. PqX509 parses, mints, checks one signature, and checks a path against caller-supplied anchors. now is an argument. It writes the PKCS#10 request openssl req verifies. cert req, cert issue, cert sign, cert inspect, and cert verify are the CLI. Signature algorithms on that path include ECDSA P-256 and P-384, Ed25519, RSA PKCS#1 and RSASSA-PSS, and ML-DSA. It is not a trust store and it does not fetch AIA, OCSP, or CT."}},{"@type":"Question","name":"Does pqforge support RC4?","acceptedAnswer":{"@type":"Answer","text":"No. RC4 is not post-quantum, not authenticated encryption, not in pqcrypto, and not safe for new systems. pqforge offers AES-256-GCM and ChaCha20-Poly1305 instead."}},{"@type":"Question","name":"Can AES sign documents?","acceptedAnswer":{"@type":"Answer","text":"No. AES encrypts; ML-DSA, hybrid signatures, or ECDSA-P256 sign and verify. Encryption and signing are distinct operations with distinct keys."}},{"@type":"Question","name":"Can encrypt/decrypt/pack/unpack report progress, and what does --quiet do?","acceptedAnswer":{"@type":"Answer","text":"encrypt, decrypt, encrypt-text, decrypt-text (when --out is set), encrypt-media, decrypt-media, encrypt-folder, decrypt-folder, pack, unpack, sign, verify, hybrid-sign, hybrid-verify, ecdsa-sign, and ecdsa-verify print a live, throttled progress line. Folder jobs forward streaming byte progress from background isolates over a SendPort so concurrent files keep separate live totals; pack/unpack add per-file SUCCESS or FAILED with in-entry byte progress. hybrid-sign/ecdsa-sign --digest reports hashing progress. keygen reports per-key wrapping progress when a passphrase is used. --quiet / -q mutes those per-file lines, skip warnings, and keygen created-file listings; the completion summary still prints. keygen --quiet still warns if raw secret-key JSON was written. A folder job that fails any file exits non-zero. Pack/unpack failures before the first entry report a job-level failure. Listing skips sockets, FIFOs, broken symlinks, and unreadable files instead of failing the whole tree. decrypt-text without --out writes plaintext to stdout and does not attach a progress line."}},{"@type":"Question","name":"Which apps can use pqforge?","acceptedAnswer":{"@type":"Answer","text":"Local file vaults, folder and pack archives, server export jobs, gigabyte media and dataset pipelines, multi-recipient shared vaults, webhook systems, token issuers, document workflows, email payload protection, government and medical record systems, signed release and firmware pipelines, tamper-evident logs, and hybrid Serverpod/API server sessions."}}]}</script>
</head>
<body>
<header class="topbar">
<a class="brand" href="#top" aria-label="pqforge home">
<span class="brand-mark">PQ</span>
<span>pqforge</span>
</a>
<div class="topbar-right">
<nav aria-label="Primary">
<a href="#recipes">Recipes</a>
<a href="#cli">CLI</a>
<a href="#use-cases">Use cases</a>
<a href="#docs">Docs</a>
<a href="#guides">Guides</a>
</nav>
<div class="topbar-links">
<a class="ext" href="https://pub.dev/packages/pqforge" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 2.5 3.5 7v10L12 21.5 20.5 17V7L12 2.5Z M3.5 7 12 11.5 20.5 7 M12 11.5V21.5"/></svg><span>pub.dev</span></a>
<a class="ext" href="https://github.com/turkananation/pqforge/wiki" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 6C10.5 4.8 8.7 4 6.5 4H3v13h4c1.9 0 3.6.6 5 1.7M12 6c1.5-1.2 3.3-2 5.5-2H21v13h-4c-1.9 0-3.6.6-5 1.7M12 6v12.7"/></svg><span>Wiki</span></a>
<a class="ext" href="https://yardenah.com" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 4h6v6H4V4Z M14 4h6v6h-6V4Z M4 14h6v6H4v-6Z M14 14h6v6h-6v-6Z"/></svg><span>Yardenah PQ</span></a>
<a class="ext" href="https://github.com/turkananation/pqforge" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="currentColor"><path d="M12 .5C5.73.5.5 5.73.5 12c0 5.08 3.29 9.39 7.86 10.91.58.11.79-.25.79-.56 0-.27-.01-1.01-.02-1.98-3.2.7-3.88-1.54-3.88-1.54-.52-1.33-1.28-1.69-1.28-1.69-1.05-.72.08-.7.08-.7 1.16.08 1.77 1.19 1.77 1.19 1.03 1.77 2.7 1.26 3.36.96.1-.75.4-1.26.73-1.55-2.55-.29-5.24-1.28-5.24-5.69 0-1.26.45-2.29 1.19-3.1-.12-.29-.52-1.46.11-3.05 0 0 .97-.31 3.18 1.18a11.1 11.1 0 0 1 5.79 0c2.2-1.49 3.17-1.18 3.17-1.18.63 1.59.23 2.76.11 3.05.74.81 1.19 1.84 1.19 3.1 0 4.42-2.69 5.39-5.25 5.68.41.36.78 1.06.78 2.14 0 1.55-.01 2.8-.01 3.18 0 .31.21.68.8.56A11.52 11.52 0 0 0 23.5 12C23.5 5.73 18.27.5 12 .5Z"/></svg><span>GitHub</span></a>
</div>
</div>
</header>
<main id="top">
<section class="hero">
<div class="hero-copy">
<p class="eyebrow">A product of <a href="https://yardenah.com" rel="noopener">Yardenah PQ</a></p>
<h1>Encrypt files, folders, text, media, webhooks, tokens, and server sessions.</h1>
<p class="lede">pqforge turns the pqcrypto ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) primitives into application-ready cryptography: KEM-DEM envelopes, RFC 9180 HPKE, X-Wing (draft-connolly-cfrg-xwing-kem-11, not a .pqf algorithm), AES-256-GCM and ChaCha20-Poly1305 AEAD, an RFC 8439 ChaCha20 keystream, X25519/X448/Ed25519/Ed448/ECDSA-P256/ECDSA-P384/ECDSA-P521/RSA hybrids and signatures, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, X.509 certificates and PKCS#10 requests that OpenSSL req reads, bounded-memory gigabyte streaming, multi-recipient envelopes, Argon2id-wrapped key custody, named recipes, and a universal CLI. SLH-DSA is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign is an opt-in 2-leg or 3-leg signature. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. The core is pure Dart and web-safe — no dart:ffi.</p>
<div class="hero-actions">
<a class="button primary" href="#cli"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 5h16a1 1 0 0 1 1 1v12a1 1 0 0 1-1 1H4a1 1 0 0 1-1-1V6a1 1 0 0 1 1-1Z M7 9.5l3 2.5-3 2.5 M13 15h4"/></svg><span>Use the CLI</span></a>
<a class="button secondary" href="#recipes"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="currentColor"><path d="M13 2 4 13h6l-1 9 9-13h-6l1-7Z"/></svg><span>Explore recipes</span></a>
<a class="button ghost" href="https://pub.dev/packages/pqforge" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 2.5 3.5 7v10L12 21.5 20.5 17V7L12 2.5Z M3.5 7 12 11.5 20.5 7 M12 11.5V21.5"/></svg><span>Install from pub.dev</span></a>
</div>
<ul class="hero-badges">
<li><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12.5 10 17.5 19.5 6.5"/></svg><span>Pure Dart, no FFI</span></li>
<li><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12.5 10 17.5 19.5 6.5"/></svg><span>Web-safe core</span></li>
<li><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12.5 10 17.5 19.5 6.5"/></svg><span>FIPS 203/204-aligned via pqcrypto</span></li>
<li><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12.5 10 17.5 19.5 6.5"/></svg><span>MIT licensed</span></li>
</ul>
</div>
<figure class="hero-visual">
<img src="assets/pqforge-protocol.png" alt="pqforge recipe pipeline from payloads to post-quantum envelopes">
</figure>
</section>
<section class="signal-grid" aria-label="Package signals">
<div><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 3 5 6v5c0 4 2.9 7 7 8 4.1-1 7-4 7-8V6l-7-3Z M9.5 11.5l1.8 1.8 3.4-3.6"/></svg><strong>3</strong><span>ML-KEM profiles</span></div>
<div><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16.5 4.5 19.5 7.5 9 18l-4 1 1-4 10.5-10.5Z M14 7l3 3"/></svg><strong>3</strong><span>ML-DSA profiles</span></div>
<div><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 3 2.5 8 12 13l9.5-5L12 3Z M2.5 12 12 17l9.5-5 M2.5 16 12 21l9.5-5"/></svg><strong>15</strong><span>named recipes</span></div>
<div><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 5h16a1 1 0 0 1 1 1v12a1 1 0 0 1-1 1H4a1 1 0 0 1-1-1V6a1 1 0 0 1 1-1Z M7 9.5l3 2.5-3 2.5 M13 15h4"/></svg><strong>1</strong><span>universal CLI</span></div>
</section>
<section id="recipes" class="section">
<div class="section-heading">
<p class="eyebrow">Recipe catalog</p>
<h2>Build with named operations, not ad hoc crypto glue.</h2>
</div>
<div class="recipes">
<article>
<span>CLI: keygen, encrypt, decrypt</span>
<h3>Local File Vault</h3>
<p>developer machines, backup jobs, admin laptops, server batch jobs</p>
<code>encryptFileBytes, decryptFileBytes, encryptAsync, PqEnvelope</code>
</article>
<article>
<span>CLI: encrypt-folder, decrypt-folder</span>
<h3>Folder Archive</h3>
<p>case files, release bundles, evidence folders, internal archives</p>
<code>encryptFolderEntry, decryptFolderEntry</code>
</article>
<article>
<span>CLI: pack, unpack</span>
<h3>Folder Pack Archive</h3>
<p>many small files, site exports, evidence bundles, dataset shards</p>
<code>PqForgePackService (package:pqforge/pqforge_io.dart)</code>
</article>
<article>
<span>CLI: encrypt / encrypt-media (auto .pqfs at 8 MiB)</span>
<h3>Large Files And Media Streaming</h3>
<p>gigabyte media, datasets, disk images, backups, VM snapshots</p>
<code>PqForgeStreamCipher.encryptFile, decryptStream (package:pqforge/pqforge_io.dart)</code>
</article>
<article>
<span>CLI: repeatable --recipient-public on encrypt commands</span>
<h3>Multi-Recipient Envelopes</h3>
<p>shared vaults, team archives, escrow, break-glass recipients</p>
<code>encryptAsync, PqMultiRecipient, PqRecipientSpec</code>
</article>
<article>
<span>CLI: encrypt-text, decrypt-text, sign --kind text</span>
<h3>Text Snippets</h3>
<p>notes, secrets, prompts, policy snippets, short messages</p>
<code>sealText, openText, signText, verifyText</code>
</article>
<article>
<span>CLI: encrypt-media, decrypt-media, sign --kind media</span>
<h3>Media Assets</h3>
<p>photos, audio, video, PDFs, campaign media, identity images</p>
<code>sealMedia, openMedia, signMedia, verifyMedia</code>
</article>
<article>
<span>CLI: sign, verify</span>
<h3>Document Signing</h3>
<p>contracts, reports, certificates, approvals, policy documents</p>
<code>signDocument, verifyDocument</code>
</article>
<article>
<span>CLI: hybrid-sign, hybrid-verify, compose-sign, compose-verify, ecdsa-sign, ecdsa-verify, cert req, cert issue, cert sign</span>
<h3>Hybrid And Classical Signatures</h3>
<p>release artifacts, firmware, long-lived approvals, dual-trust signing</p>
<code>PqForgeHybridSigner, PqForgeSignatureComposer, PqEcdsaP256, PqEcdsaP384, PqEcdsaP521, PqEd25519, PqEd448, PqRsa, PqX509, dualSign, dualVerify</code>
</article>
<article>
<span>CLI: sign --kind webhook, verify</span>
<h3>Webhook Integrity</h3>
<p>payment callbacks, audit delivery, server-to-server events</p>
<code>signWebhook, verifyWebhook</code>
</article>
<article>
<span>library</span>
<h3>Signed Tokens</h3>
<p>API capabilities, admin actions, short-lived grants</p>
<code>issueToken, verifyToken</code>
</article>
<article>
<span>library</span>
<h3>Private Email Payloads</h3>
<p>encrypted mail bodies, secure notifications, outbound archive mail</p>
<code>sealEmail, openEmail</code>
</article>
<article>
<span>library</span>
<h3>Government And Medical Records</h3>
<p>public-sector records, patient records, registry payloads</p>
<code>encryptRecord, appendSignedLogEntry</code>
</article>
<article>
<span>CLI/library</span>
<h3>Software Artifacts</h3>
<p>release bundles, firmware, packages, configuration rollouts</p>
<code>signArtifact, verifyArtifact</code>
</article>
<article>
<span>core import (package:pqforge/pqforge.dart)</span>
<h3>Hybrid Server Sessions</h3>
<p>Serverpod, API services, local agents, backend handshakes</p>
<code>PqForgeHybridKeyAgreement, PqForgeSecureSession</code>
</article>
</div>
</section>
<section id="cli" class="section split">
<div>
<p class="eyebrow">Universal CLI</p>
<h2>Local files and server jobs get the same envelope model.</h2>
<p>Generate reusable public keys and wrapped secret keys, then encrypt or sign files, folders, text, and media without writing application code.</p>
</div>
<pre class="terminal"><code>export PQFORGE_PASSPHRASE='from-your-secret-manager'
dart run pqforge keygen --profile maximum --key-id vault --out-dir keys --passphrase-env PQFORGE_PASSPHRASE
dart run pqforge encrypt-folder --recipient-public keys/vault.kem.public.json --in-dir ./records --out-dir ./records.pqf
dart run pqforge decrypt-folder --recipient-secret keys/vault.kem.secret.wrapped.json --passphrase-env PQFORGE_PASSPHRASE --in-dir ./records.pqf --out-dir ./records.open
dart run pqforge sign --kind media --signer-secret keys/vault.sign.secret.wrapped.json --passphrase-env PQFORGE_PASSPHRASE --in cover.png --mime-type image/png --out cover.sig.json
dart run pqforge compose-sign --ml-dsa-secret keys/vault.sign.secret.wrapped.json --classical-secret keys/vault.ecdsa-p256.secret.wrapped.json --passphrase-env PQFORGE_PASSPHRASE --in cover.png --out cover.composite.json</code></pre>
</section>
<section id="use-cases" class="section">
<div class="section-heading">
<p class="eyebrow">Use cases</p>
<h2>From local vaults to server sessions.</h2>
</div>
<div class="use-cases">
<div><h3>Local File Vault</h3><p>developer machines, backup jobs, admin laptops, server batch jobs</p></div>
<div><h3>Folder Archive</h3><p>case files, release bundles, evidence folders, internal archives</p></div>
<div><h3>Folder Pack Archive</h3><p>many small files, site exports, evidence bundles, dataset shards</p></div>
<div><h3>Large Files And Media Streaming</h3><p>gigabyte media, datasets, disk images, backups, VM snapshots</p></div>
<div><h3>Multi-Recipient Envelopes</h3><p>shared vaults, team archives, escrow, break-glass recipients</p></div>
<div><h3>Text Snippets</h3><p>notes, secrets, prompts, policy snippets, short messages</p></div>
<div><h3>Media Assets</h3><p>photos, audio, video, PDFs, campaign media, identity images</p></div>
<div><h3>Document Signing</h3><p>contracts, reports, certificates, approvals, policy documents</p></div>
<div><h3>Hybrid And Classical Signatures</h3><p>release artifacts, firmware, long-lived approvals, dual-trust signing</p></div>
<div><h3>Webhook Integrity</h3><p>payment callbacks, audit delivery, server-to-server events</p></div>
<div><h3>Signed Tokens</h3><p>API capabilities, admin actions, short-lived grants</p></div>
<div><h3>Private Email Payloads</h3><p>encrypted mail bodies, secure notifications, outbound archive mail</p></div>
<div><h3>Government And Medical Records</h3><p>public-sector records, patient records, registry payloads</p></div>
<div><h3>Software Artifacts</h3><p>release bundles, firmware, packages, configuration rollouts</p></div>
<div><h3>Hybrid Server Sessions</h3><p>Serverpod, API services, local agents, backend handshakes</p></div>
</div>
</section>
<section class="section profiles">
<div class="section-heading">
<p class="eyebrow">Profiles</p>
<h2>Pick a security margin that matches the lifetime.</h2>
</div>
<div class="profile-grid">
<div><h3>compact</h3><p>ML-KEM-512 + ML-DSA-44</p><span>smaller demos, constrained payloads, and low-bandwidth signatures</span></div>
<div><h3>balanced</h3><p>ML-KEM-768 + ML-DSA-65</p><span>default application and server profile</span></div>
<div><h3>maximum</h3><p>ML-KEM-1024 + ML-DSA-87</p><span>long-lived records, archives, media, and high-value artifacts</span></div>
</div>
</section>
<section id="docs" class="section docs">
<div class="section-heading">
<p class="eyebrow">Documentation</p>
<h2>Everything users and agents need to stay inside the boundary.</h2>
</div>
<div class="doc-grid">
<a href="https://github.com/turkananation/pqforge/blob/main/README.md"><strong>README</strong><span>High-signal overview, badges, quickstarts, recipe map, and validation commands.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/INDEX.md"><strong>Documentation Index</strong><span>Canonical map of every doc, the package surface, and the visibility generator.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/CLI.md"><strong>CLI Guide</strong><span>Full command-line usage: wrapped keys, files, folders, text, media, streaming, pack, multi-recipient, hybrid, and signatures.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/cookbook/PROJECT_CATALOG.md"><strong>Project Catalog</strong><span>Applications and domains that map to pqforge recipes.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/cookbook/README.md"><strong>Recipe Cookbook</strong><span>Named recipe docs for safe application composition.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/API.md"><strong>API Reference</strong><span>Facade methods, hybrid tier, secure sessions, AEAD engines, types, and CLI summary.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/HYBRID_AUDIT.md"><strong>Hybrid Audit</strong><span>Coverage audit against pqcrypto: composed ML-KEM/ML-DSA, SLH-DSA keygen and detached signatures, and explicit rejections.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/technical/PERFORMANCE_AUDIT_AND_HYBRID_CLI.md"><strong>Performance And Hybrid CLI</strong><span>As-built throughput, memory, and engine/cipher recommendations with measured numbers.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/architecture/ENVELOPE_FORMATS.md"><strong>Envelope Formats</strong><span>The .pqf one-shot and .pqfs streaming container layouts and AAD binding.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/security/THREAT_MODEL.md"><strong>Threat Model</strong><span>Assets, adversaries, what the package defends, and what the application must own.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/architecture/KEY_CUSTODY.md"><strong>Key Custody</strong><span>Wrapped key storage and pluggable custody model.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/protocols/HPKE.md"><strong>HPKE</strong><span>RFC 9180 HPKE: modes, suites, seal/open/export, and the BoringSSL interop boundary. X-Wing is the additional KEM in XWING.md.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/protocols/XWING.md"><strong>X-Wing</strong><span>draft-connolly-cfrg-xwing-kem-11 as PqXWing and HpkeKem.xWing (0x647A). Not the custom hybrid and not a .pqf algorithm.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/site/content/signatures.md"><strong>Signatures</strong><span>Opt-in dual and triple signature legs. Does not replace HPKE, certificates, ECDH, or envelope signatures.</span></a>
<a href="https://github.com/turkananation/pqforge/blob/main/doc/security/CLAIM_BOUNDARY.md"><strong>Claim Boundary</strong><span>Allowed and forbidden claims for package consumers and agents.</span></a>
</div>
</section>
<section id="guides" class="section">
<div class="section-heading">
<p class="eyebrow">On this site</p>
<h2>The recipe homepage stays. The guides sit next to it.</h2>
</div>
<div class="doc-grid">
<a href="release-notes"><strong>What landed</strong><span>0.4.13 RSA verification accepts a 1024-bit modulus, 0.4.12 brainpool and RFC 7919 finite-field agreement, 0.4.11 SHA-1 for a standard that still names it, 0.4.10 HPKE, 0.4.9 certificates, 0.4.8 ChaCha20, and the signature legs. This does not replace the recipe catalog above.</span></a>
<a href="getting-started"><strong>Getting started</strong><span>Install pqforge and seal one HPKE message.</span></a>
<a href="agreement"><strong>Agreement</strong><span>Brainpool, RFC 7919 FFDHE, NIST ECDH, X25519, X448, and the combiner. Not a TLS stack.</span></a>
<a href="envelopes"><strong>Envelopes</strong><span>Profiles, .pqf, .pqfs, multi-recipient wrap, and hybrid KEM-DEM.</span></a>
<a href="keys"><strong>Keys</strong><span>Keygen, Argon2id, PBKDF2, and pluggable custody.</span></a>
<a href="hpke"><strong>HPKE</strong><span>RFC 9180 modes, suites, seal, auth, and export.</span></a>
<a href="certificates"><strong>Certificates</strong><span>X.509 and PKCS#10. Not a trust store.</span></a>
<a href="symmetric"><strong>Symmetric</strong><span>AES-GCM, ChaCha20-Poly1305, the ChaCha20 keystream, and session packets.</span></a>
<a href="bytes"><strong>Bytes</strong><span>SHA-1, SHA-2, HMAC, and length prefixes.</span></a>
<a href="classical"><strong>Classical</strong><span>X25519, X448, NIST ECDH, Ed25519, ECDSA, and RSA. P-521 ECDH is still the HPKE share.</span></a>
<a href="signatures"><strong>Signatures</strong><span>Opt-in dual and triple legs. hybrid-sign stays one ML-DSA leg plus one classical leg.</span></a>
<a href="recipes"><strong>Recipes</strong><span>Identity bindings, signed logs, tokens, and artifacts.</span></a>
<a href="cli"><strong>CLI</strong><span>Every command, and which API it calls.</span></a>
<a href="claim-boundary"><strong>Claim boundary</strong><span>What this package is allowed to say about itself.</span></a>
</div>
</section>
<section class="section boundary">
<div>
<p class="eyebrow">Claim boundary</p>
<h2>Composition, not certification.</h2>
<p>pqforge is the application layer built on <a href="https://pub.dev/packages/pqcrypto">pqcrypto</a> ML-KEM/ML-DSA. It does not claim CMVP/FIPS 140 validation, hard constant-time Dart behavior, or hard memory erasure. RC4 is rejected.</p>
</div>
<ul>
<li>ML-KEM-512/768/1024 KEM-DEM envelopes through pqcrypto (FIPS 203-aligned)</li>
<li>ML-DSA-44/65/87 detached and pre-hash signatures through pqcrypto (FIPS 204-aligned)</li>
<li>SLH-DSA (FIPS 205, all 12 parameter sets) composed into keygen, custody, and detached sign/verify; not used for envelopes or hybrid-sign. compose-sign can take one SLH-DSA leg when that key is passed</li>
<li>AES-256-GCM and ChaCha20-Poly1305 AEAD on a pure-Dart (PointyCastle) or native (package:cryptography) engine</li>
<li>RFC 8439 ChaCha20 keystream (PqSymmetricPrimitives.chacha20) for a QUIC header-protection mask. Not an AEAD</li>
<li>RFC 9180 HPKE (PqHpke): base, PSK, auth, and authPSK. KEMs DHKEM X25519, X448, P-256, P-384, and P-521. KDFs HKDF-SHA256, SHA384, and SHA512. AEADs AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305, and export-only. BoringSSL 0.20261020.0 interop is base and auth, X25519 and P-256, HKDF-SHA256/384, and the three AEADs. OpenSSL 3.5.9 OSSL_HPKE interop is all four modes, X448 and P-521, HKDF-SHA256/512, and the three AEADs. Not a BoringSSL claim for X448 or P-521. Not an OpenSSL claim for X25519, P-256, or P-384. X-Wing (HpkeKem.xWing, 0x647A, draft-connolly-cfrg-xwing-kem-11) is an additional base and PSK KEM. Auth is rejected. Not a FIPS construction. Not a .pqf or .pqfs algorithm. No BoringSSL or OpenSSL evidence for 0x647A</li>
</ul>
</section>
<section class="section faq">
<div class="section-heading">
<p class="eyebrow">FAQ</p>
<h2>Answers before integration.</h2>
</div>
<details><summary>What is pqforge?</summary><p>pqforge is a pure-Dart post-quantum application toolkit. It turns the ML-KEM, ML-DSA, and SLH-DSA primitives from pqcrypto into encrypted files, folders, text, media, email payloads, records, signed documents, signed webhooks, signed tokens, release artifacts, tamper-evident logs, identity bindings, hybrid sessions, wrapped key custody, and a universal CLI. SLH-DSA (FIPS 205) is composed into keygen, custody, and detached sign/verify; envelopes and hybrid-sign remain ML-DSA-only. compose-sign can take one SLH-DSA leg when that key is passed.</p></details>
<details><summary>How is pqforge different from pqcrypto?</summary><p>pqcrypto is the primitives layer: FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA (all 12 parameter sets), SHA-2, and SHA-3/SHAKE with zero runtime dependencies. pqforge is the application layer built on top of it: KEM-DEM envelopes, AES-256-GCM and ChaCha20-Poly1305 AEAD, RFC 9180 HPKE (X25519, X448, P-256, P-384, P-521), X25519/Ed25519/ECDSA-P256 hybrids plus opt-in ECDSA-P384 and ECDSA-P521, P-256/P-384 ECDH for TLS hybrid groups and P-521 ECDH for HPKE, key custody, streaming, multi-recipient envelopes, named recipes, compose-sign, and a CLI. SLH-DSA is composed into keygen and detached sign/verify, and is not used for envelopes or hybrid-sign. PqEcdsaP521 is not the P-521 HPKE share and not a TLS group. Use pqcrypto for raw algorithms; use pqforge to ship a feature.</p></details>
<details><summary>Does pqforge compose SLH-DSA?</summary><p>Yes, for key generation, custody, and detached signatures. pqcrypto 0.4.4 ships all 12 FIPS 205 SLH-DSA parameter sets. pqforge exposes them as PqSlhDsaAlgorithm / PqSlhDsaPrimitives, emits a profile-matched SHAKE-f key from keygen (compact 128f, balanced 192f, maximum 256f), and accepts those keys on sign/verify (document, text, media, artifact, webhook) and on issueToken, appendSignedLogEntry, and createIdentityBinding via slhDsa:. Envelope headers, streaming signatures, and hybrid-sign remain ML-DSA-only because SLH-DSA signatures are 8-50 KiB and the s sets are slow. compose-sign can take one SLH-DSA leg when you pass that key. That does not put SLH-DSA on an envelope or on hybrid-sign.</p></details>
<details><summary>Is pqforge post-quantum / quantum-safe?</summary><p>Yes. It uses NIST FIPS 203 ML-KEM for key establishment and FIPS 204 ML-DSA for signatures through pqcrypto, so confidentiality and signatures resist quantum attacks. Hybrid modes add X25519, Ed25519, or ECDSA-P256 so security also holds if a classical break ever lands on the post-quantum scheme.</p></details>
<details><summary>Does pqforge work on Flutter and the web?</summary><p>Yes. The core import, package:pqforge/pqforge.dart, is pure Dart and web-safe with no dart:ffi, so the same code runs on the Dart VM, Flutter, and the web. Gigabyte-scale dart:io file streaming lives behind package:pqforge/pqforge_io.dart. On Flutter, FlutterCryptography.enable() adds hardware-backed AEAD.</p></details>
<details><summary>Can pqforge encrypt gigabyte files without running out of memory?</summary><p>Yes. Inputs at or above 8 MiB automatically use the .pqfs streaming container: a signed master header followed by independently authenticated frames, with a working set of roughly two frames regardless of total size. Per-frame sequence and final-flag binding prevent truncation, reordering, duplication, and splicing.</p></details>
<details><summary>Can one ciphertext target multiple recipients?</summary><p>Yes. Repeat --recipient-public on the encrypt commands (or use PqMultiRecipient in the library). The payload is sealed exactly once and the DEM key is wrapped to each additional recipient as a metadata entry, costing about 1.6 KB and 2 ms per extra recipient instead of a full re-encryption. Entries can individually be hybrid, and it works for both one-shot envelopes and .pqfs streams.</p></details>
<details><summary>Which ciphers does pqforge support, and which is fastest?</summary><p>AES-256-GCM (default) and ChaCha20-Poly1305, on a pure-Dart PointyCastle engine or the native package:cryptography engine. Where hardware AES is not dispatched, ChaCha20-Poly1305 measures about 30.4 MiB/s versus 11.5 MiB/s for AES-256-GCM (about 2.6x); with hardware AEAD both exceed 1 GB/s. RC4 is rejected.</p></details>
<details><summary>What is the difference between the cryptography and pure-dart engines?</summary><p>--engine cryptography (the default) uses package:cryptography and is roughly 10x faster than the PointyCastle reference even in pure Dart, and hardware-backed on Flutter. --engine pure-dart uses PointyCastle only. The wire formats are engine-independent, so an envelope sealed by one engine opens on the other.</p></details>
<details><summary>Is pqforge FIPS validated?</summary><p>No. pqforge composes FIPS 203/204/205-aligned primitives from pqcrypto, but is not a CMVP or FIPS 140 validated cryptographic module. A PqFipsMode deployment layer restricts suites to AES-256-GCM and PBKDF2-HMAC-SHA256 key wrapping (SP 800-132) and allows a swappable DRBG for validated-module deployments.</p></details>
<details><summary>Can pqforge sign and verify documents and releases?</summary><p>Yes. It provides ML-DSA detached signatures, recipe-bound signatures for documents, text, media, artifacts, tokens, and webhooks, SLH-DSA (FIPS 205) detached signatures via keygen and sign/verify, hybrid ML-DSA + Ed25519/ECDSA-P256 signatures, and standalone ECDSA-P256 (RFC 6979 deterministic nonces, canonical low-S). AES never signs.</p></details>
<details><summary>Can I sign a gigabyte artifact without reading it all into memory?</summary><p>Yes. hybrid-sign --digest and ecdsa-sign --digest sign the streamed SHA-256 of the input under a domain-separation label, recorded in the signature JSON so the verify commands re-hash automatically. Envelope signatures are likewise computed over a header-plus-payload hash, so signing cost does not scale with payload size.</p></details>
<details><summary>Can pqforge bundle a whole folder into one file?</summary><p>Yes. pqforge pack collapses a whole folder into one encrypted streaming archive with a single KEM encapsulation and signature for the tree, roughly 100x less ciphertext overhead than per-file envelopes for a thousand small files. pqforge unpack restores it path-traversal-safe, and a failed unpack removes everything it created.</p></details>
<details><summary>What does hybrid mean in pqforge?</summary><p>Two independent hard problems guard the same secret. Hybrid encryption combines the ML-KEM shared secret with an ephemeral X25519 exchange using the IETF concatenate-then-KDF construction, so confidentiality holds while either Module-LWE or Curve25519 stands. Hybrid signatures pair an ML-DSA signature with an Ed25519 or ECDSA-P256 signature over the same message. That hybrid command also accepts opt-in ECDSA-P384 and ECDSA-P521. compose-sign is separate: 2 or 3 legs you name, among ML-DSA, SLH-DSA, Ed25519, and those ECDSA curves. ECDSA-P384 and ECDSA-P521 are keygen --classical opt-ins, not the default set. PqEcdsaP521 is not a TLS group and not the HPKE share. Library-only NIST P-256/P-384 ECDH (uncompressed SEC1, x-coordinate secret) is exported for TLS hybrid groups; it is not the X25519 initiate/accept handshake and does not overload PqEcdsaP256. PqEcdsaP384 is the P-384 signature, not that shared secret. PqX509 parses, mints, and checks an X.509 certificate, and it writes the PKCS#10 request openssl req verifies. cert req, cert issue, and cert sign are that CLI. It is not a trust store and not TLS.</p></details>
<details><summary>Where does the CLI store keys?</summary><p>In the directory passed to keygen --out-dir. Public keys are raw JSON. Secret keys are wrapped JSON when a passphrase source is supplied. keygen emits the full hybrid keyset by default: ML-KEM and ML-DSA, a profile-matched SLH-DSA SHAKE-f key, plus X25519, Ed25519, and ECDSA-P256. --no-slh-dsa skips hash-based keys; --slh-dsa selects specific FIPS 205 sets; --slh-dsa-only emits only SLH-DSA.</p></details>
<details><summary>Are CLI keys password protected?</summary><p>Yes when keygen is run with --passphrase-env, --passphrase-file, or --passphrase. Wrapped secrets use Argon2id for passphrase-to-key derivation and AES-256-GCM for authenticated encryption of the key bytes, with AAD binding the key kind, algorithm, and key id.</p></details>
<details><summary>Can I inspect an encrypted file without decrypting it?</summary><p>Yes. pqforge inspect describes any .pqf, .pqfs, key, or signature file: format, profile, suite (for example ML-KEM-1024 + X25519 then HKDF-SHA-512 then AES-256-GCM), engine, signature, recipients, and metadata, without needing a secret key.</p></details>
<details><summary>Does pqforge provide identity, trust, or replay protection?</summary><p>No. pqforge composes cryptographic building blocks. Public-key trust, identity vetting, replay windows, authorization policy, session storage, and TLS remain the application's responsibility. A self-provided public key is not an identity.</p></details>
<details><summary>Is the published package pure Dart? Does it use FFI?</summary><p>Yes, it is pure Dart with no dart:ffi, so it runs everywhere Dart runs, including the web. The OpenSSL interop harness used in CI to prove byte-compatibility with the system libcrypto is a separate publish_to: none dev package and is never shipped.</p></details>
<details><summary>What HPKE does pqforge implement?</summary><p>RFC 9180 Hybrid Public Key Encryption as PqHpke. Modes are base, PSK, auth, and authPSK. KEMs are DHKEM(X25519, HKDF-SHA256), DHKEM(X448, HKDF-SHA512), DHKEM(P-256, HKDF-SHA256), DHKEM(P-384, HKDF-SHA384), and DHKEM(P-521, HKDF-SHA512). X-Wing is an additional KEM, HpkeKem.xWing, id 0x647A, from draft-connolly-cfrg-xwing-kem-11. It is not a DHKEM. Base and PSK work. Auth and authPSK throw. It is not a FIPS construction. FIPS mode rejects it at PqHpke and PqForgeHybridKeyAgreement. There is no BoringSSL or OpenSSL evidence for 0x647A. pqforge hpke writes magic XW01, not PQF1. The custom hybrid is unchanged. Key-schedule KDFs are HKDF-SHA256, HKDF-SHA384, and HKDF-SHA512. AEADs are AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305, and export-only. A sender seals, a recipient opens, and export does not use the sequence number. X448 is RFC 7748 on Dart integers and is not a constant-time claim. BoringSSL 0.20261020.0 is checked for base and auth, both directions, on X25519 and P-256, with HKDF-SHA256 and HKDF-SHA384 and the three AEADs. That API has no PSK and no X448 or P-521. OpenSSL 3.5.9 OSSL_HPKE is checked for all four modes, both directions, on X448 and P-521, with HKDF-SHA256 and HKDF-SHA512 and the three AEADs. That is not an OpenSSL claim for X25519, P-256, or P-384. This is not TLS and not a FIPS module. .pqf and .pqfs are unchanged.</p></details>
<details><summary>What is the ChaCha20 keystream for?</summary><p>PqSymmetricPrimitives.chacha20 is RFC 8439 ChaCha20. It takes a 32-byte key, a 12-byte nonce, a caller-supplied 32-bit block counter, and returns 1 to 4096 keystream bytes. QUIC header protection uses the first 5 bytes. It is the same Dart engine as chacha20Poly1305Encrypt, so it runs on dart2js. It is not an AEAD: the AEAD forces counter 1 and appends a Poly1305 tag.</p></details>
<details><summary>Does pqforge read and mint X.509 certificates?</summary><p>Yes. PqX509 parses, mints, checks one signature, and checks a path against caller-supplied anchors. now is an argument. It writes the PKCS#10 request openssl req verifies. cert req, cert issue, cert sign, cert inspect, and cert verify are the CLI. Signature algorithms on that path include ECDSA P-256 and P-384, Ed25519, RSA PKCS#1 and RSASSA-PSS, and ML-DSA. It is not a trust store and it does not fetch AIA, OCSP, or CT.</p></details>
<details><summary>Does pqforge support RC4?</summary><p>No. RC4 is not post-quantum, not authenticated encryption, not in pqcrypto, and not safe for new systems. pqforge offers AES-256-GCM and ChaCha20-Poly1305 instead.</p></details>
<details><summary>Can AES sign documents?</summary><p>No. AES encrypts; ML-DSA, hybrid signatures, or ECDSA-P256 sign and verify. Encryption and signing are distinct operations with distinct keys.</p></details>
<details><summary>Can encrypt/decrypt/pack/unpack report progress, and what does --quiet do?</summary><p>encrypt, decrypt, encrypt-text, decrypt-text (when --out is set), encrypt-media, decrypt-media, encrypt-folder, decrypt-folder, pack, unpack, sign, verify, hybrid-sign, hybrid-verify, ecdsa-sign, and ecdsa-verify print a live, throttled progress line. Folder jobs forward streaming byte progress from background isolates over a SendPort so concurrent files keep separate live totals; pack/unpack add per-file SUCCESS or FAILED with in-entry byte progress. hybrid-sign/ecdsa-sign --digest reports hashing progress. keygen reports per-key wrapping progress when a passphrase is used. --quiet / -q mutes those per-file lines, skip warnings, and keygen created-file listings; the completion summary still prints. keygen --quiet still warns if raw secret-key JSON was written. A folder job that fails any file exits non-zero. Pack/unpack failures before the first entry report a job-level failure. Listing skips sockets, FIFOs, broken symlinks, and unreadable files instead of failing the whole tree. decrypt-text without --out writes plaintext to stdout and does not attach a progress line.</p></details>
<details><summary>Which apps can use pqforge?</summary><p>Local file vaults, folder and pack archives, server export jobs, gigabyte media and dataset pipelines, multi-recipient shared vaults, webhook systems, token issuers, document workflows, email payload protection, government and medical record systems, signed release and firmware pipelines, tamper-evident logs, and hybrid Serverpod/API server sessions.</p></details>
</section>
</main>
<footer>
<span>Generated from tool/visibility/visibility_manifest.json</span>
<a href="https://github.com/turkananation/pqforge" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="currentColor"><path d="M12 .5C5.73.5.5 5.73.5 12c0 5.08 3.29 9.39 7.86 10.91.58.11.79-.25.79-.56 0-.27-.01-1.01-.02-1.98-3.2.7-3.88-1.54-3.88-1.54-.52-1.33-1.28-1.69-1.28-1.69-1.05-.72.08-.7.08-.7 1.16.08 1.77 1.19 1.77 1.19 1.03 1.77 2.7 1.26 3.36.96.1-.75.4-1.26.73-1.55-2.55-.29-5.24-1.28-5.24-5.69 0-1.26.45-2.29 1.19-3.1-.12-.29-.52-1.46.11-3.05 0 0 .97-.31 3.18 1.18a11.1 11.1 0 0 1 5.79 0c2.2-1.49 3.17-1.18 3.17-1.18.63 1.59.23 2.76.11 3.05.74.81 1.19 1.84 1.19 3.1 0 4.42-2.69 5.39-5.25 5.68.41.36.78 1.06.78 2.14 0 1.55-.01 2.8-.01 3.18 0 .31.21.68.8.56A11.52 11.52 0 0 0 23.5 12C23.5 5.73 18.27.5 12 .5Z"/></svg><span>GitHub</span></a>
<a href="https://pub.dev/packages/pqforge" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 2.5 3.5 7v10L12 21.5 20.5 17V7L12 2.5Z M3.5 7 12 11.5 20.5 7 M12 11.5V21.5"/></svg><span>pub.dev</span></a>
<a href="https://github.com/turkananation/pqforge/wiki" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 6C10.5 4.8 8.7 4 6.5 4H3v13h4c1.9 0 3.6.6 5 1.7M12 6c1.5-1.2 3.3-2 5.5-2H21v13h-4c-1.9 0-3.6.6-5 1.7M12 6v12.7"/></svg><span>Wiki</span></a>
<a href="https://yardenah.com" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 4h6v6H4V4Z M14 4h6v6h-6V4Z M4 14h6v6H4v-6Z M14 14h6v6h-6v-6Z"/></svg><span>A product of Yardenah PQ</span></a>
<a href="https://pub.dev/packages/pqcrypto" rel="noopener"><svg class="i" viewBox="0 0 24 24" aria-hidden="true" focusable="false" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 4h6v6H4V4Z M14 4h6v6h-6V4Z M4 14h6v6H4v-6Z M14 14h6v6h-6v-6Z"/></svg><span>pqcrypto</span></a>
</footer>
</body>
</html>