quic-go is ready for FIPS 140-3
How quic-go became ready for FIPS 140-3
(untitled)
Recent content on
Latest posts
Using nftables for QUIC load balancing
Using nftables to load balance QUIC connections
Rewriting quic-go's test suite
Rewriting quic-go's test suite
Revamping the quic-go API: Transitioning from Interfaces to Structs
Revamping the quic-go API: Transitioning from Interfaces to Structs
Controlling IP Fragmentation for Path MTU Discovery
How IP fragmentation works and why it is important for QUIC
A p2p Vision for QUIC
Using QUIC to achieve everything needed for NAT traversal, from address discovery to proxying UDP
Exploiting QUIC’s Connection ID Management
QUIC’s connection ID issuance mechanism is vulnerable to a resource exhaustion attack similar to the recently reported attack against QUIC’s path validation mechanism . I discovered this vulnerability in December 2023 and disclosed it to the IETF QUIC working group. Among 17 QUIC stacks surveyed, 11 were found vulnerable, including my own ( quic-go ), Cloudflare quiche , Neqo (Mozilla), lsquic…
Exploiting QUIC's Path Validation
QUIC supports connection migration, allowing the client to migrate an established QUIC connection from one path to the other. QUIC’s path validation mechanism can be used to attack the peer and make it consume an unbounded amount of memory. While there have been a number of vulnerabilities in various QUIC implementations, this vulnerability is the first attack against the QUIC protocol itself,…