pqtransport logopqtransport

Platform Support

VM, Flutter, and web support for pqtransport. Verified by barrels, not prose.

pqtransport targets Dart SDK >=3.12.0 <4.0.0. Cryptography is pure-Dart via pqforge (no dart:ffi in this package). Which transports work depends on the barrel and the host.

Barrels#

ImportPlatformsProvides
package:pqtransport/pqtransport.dart VM, Flutter, web TLS, HTTP/1.1–2, DNSSEC, DoH codecs, hybrid, memory sockets, QUIC packet protection
package:pqtransport/pqtransport_io.dart Dart VM, Flutter mobile/desktop Plus IoDatagramChannel, IoTcpSocket, IoTcpServer

Matrix#

CapabilityVMFlutterWeb
In-memory TLSYesYesYes
ChaCha20-Poly1305 (0x1303) Yes Yes Yes (pqforge 0.4.5 Dart engine). AES-GCM 0x1302 is the default.
HTTP/1.1 over that TLSYesYesYes
HTTP/2 over that TLS (ALPN h2)YesYesYes
DNS codec / cache / breakerYesYesYes
Encrypted UDP (memory)YesYesYes
Encrypted UDP (real NIC)YesYesNo
mDNS on a real LAN Yes (joinMulticast) Yes No
DNSSEC validate / iterative resolve Yes Yes Yes. The network send is the caller's
QUIC / HTTP/3 OpenSSL 3.5.9 QUIC both ways is a handshake (ML-DSA-65). Client peer is demos/quic/server , ALPN ossltest . quiche 0.30.0 completes one HTTP/3 GET both ways (bodies pq-h3 and quiche-h3 ). Not a complete RFC 9114 stack. Not curl --http3 . QPACK field sections also round-trip with nghttp3 1.11.0 Same handshake on the VM No raw UDP
OpenSSL 3.5.9 / BoringSSL 0.20261020.0 The Peers job Same code Not a browser
SecureSocket on PQ pathNot usedNot usedNot used

Browsers do not expose generic UDP, multicast, or a raw QUIC socket. Web callers supply a PqTransportSocket over whatever byte pipe they have (WebSocket, a VM sidecar, MemoryByteSocket in tests) and run PqTlsSocket on that pipe.