# QUIC

QUIC is a UDP-based multiplexed and secure transport protocol that provides flow-controlled streams, low-latency connection establishment, and network path migration.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments

DevFeed: [QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments](<https://devfeed.tech/articles/quic-and-covert-novel-http-3-powered-rats-target-southeast-asian-governments-136359.md>)

Original publisher: [Read original article](<https://unit42.paloaltonetworks.com/custom-rats-target-southeast-asia-governments/>)

Author: Tom Fakterman

Published: 2026-11-16T23:00:55Z

Content type: news

Language: en

Sources: [Unit 42](<https://devfeed.tech/sources/unit-42.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [backdoor](<https://devfeed.tech/tags/backdoor.md>), [credential-harvesting](<https://devfeed.tech/tags/credential-harvesting.md>), [cyberespionage](<https://devfeed.tech/tags/cyberespionage.md>), [data-exfiltration](<https://devfeed.tech/tags/data-exfiltration.md>), [dll-sideloading](<https://devfeed.tech/tags/dll-sideloading.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [malware](<https://devfeed.tech/tags/malware.md>), [modular](<https://devfeed.tech/tags/modular.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [quic](<https://devfeed.tech/tags/quic.md>), [rat](<https://devfeed.tech/tags/rat.md>), [shellcode](<https://devfeed.tech/tags/shellcode.md>), [tgr-sta-0049](<https://devfeed.tech/tags/tgr-sta-0049.md>), [threat-research](<https://devfeed.tech/tags/threat-research.md>), [xor](<https://devfeed.tech/tags/xor.md>)

### AI overview

Unit 42 reports that TGR-STA-0049 has targeted government and other high-value organizations since at least 2023, with a Southeast Asia-focused campaign deploying PerfectPioneer RAT from mid-2025 and its modular successor KUKURAT from March 2026. Both use HTTP/3 over QUIC for command and control in some variants; PerfectPioneer falls back to HTTP/2, while KUKURAT has separate HTTP/2 and HTTP/3 variants. PerfectPioneer combines broad host-control features with routines for reconnection, cleanup and blocking operator commands considered noisy or destructive. KUKURAT loads capabilities dynamically and can generate configurable decoy network, registry and file activity. The campaign used server exploitation and phishing for access, then credential theft, logon-script propagation and attempts to exfiltrate documents and access Exchange mailboxes. The report recommends inspecting or restricting outbound QUIC, auditing Active Directory logon scripts and Exchange impersonation/access rights, and detecting ordinal-based LSASS dumping.

### Source excerpt

We uncover a Southeast Asian cyberespionage campaign deploying PerfectPioneer RAT, modular KUKURAT and stealth HTTP/3 C2 communication channels. The post QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments appeared first on Unit 42.

## CVE-2026-12708 - Unbounded HTTP/3 Datagram flow map growth in tokio-quiche

DevFeed: [CVE-2026-12708 - Unbounded HTTP/3 Datagram flow map growth in tokio-quiche](<https://devfeed.tech/articles/cve-2026-12708-unbounded-http-3-datagram-flow-map-growth-in-tokio-quiche-126434.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-12708>)

Author: cvefeed.io

Published: 2026-11-10T14:17:29Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>)

Tags: [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cve-2026-12708](<https://devfeed.tech/tags/cve-2026-12708.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [memory](<https://devfeed.tech/tags/memory.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [quic](<https://devfeed.tech/tags/quic.md>), [quiche](<https://devfeed.tech/tags/quiche.md>), [remediation](<https://devfeed.tech/tags/remediation.md>)

### AI overview

CVE-2026-12708 is a high-severity denial-of-service flaw in tokio-quiche's HTTP/3 DATAGRAM handling: a peer can send DATAGRAMs with many distinct flow identifiers, making per-connection flow and channel state grow without bound and potentially exhausting memory. Both client and server configurations are exposed when DATAGRAM support is negotiated; deployments without it are not affected. Mitigate by setting QuicSettings::enable_dgram to false, or upgrade to tokio-quiche 0.23.0 or later. The fix limits flow state to valid DATAGRAM-capable request streams; servers use a bounded, expiring buffer for early packets, while clients discard packets for unknown flows.

### Source excerpt

CVE ID :CVE-2026-12708 Published : Nov. 10, 2026, 2:17 p.m. | 1 hour, 13 minutes ago Description :Summary Cloudflare tokio-quiche was found to contain an uncontrolled resource consumption vulnerability in its HTTP/3 DATAGRAM handling. For every previously unseen flow identifier (quarter stream ID) received in a DATAGRAM frame, tokio-quiche creates and retains new, per-flow state. A remote peer can send DATAGRAMs with many distinct identifiers, causing the per-connection flow map and associated channel state to grow without bound. Impact Exploitation can exhaust process memory and cause a denial of service. The vulnerable code is used in both client and server configurations, so either role can be affected by a malicious peer. QUIC DATAGRAM support in tokio-quiche is enabled by default through QuicSettings::enable_dgram; applications can disable it by setting this field to false. The vulnerable HTTP/3 path is reachable only when DATAGRAM support is negotiated with the peer. Core quiche and HTTP/3 deployments without DATAGRAM support are not affected. Mitigation Disable DATAGRAMs in tokio-quiche's QuicSettings::enable_dgram. Remediation Upgrade to tokio-quiche version 0.23.0 or later. The fixed code creates flow state only for valid DATAGRAM-capable request streams, which are bounded by QUIC's stream limits. To tolerate packet reordering, servers retain early DATAGRAMs in a bounded, expiring buffer, while clients discard DATAGRAMs for unknown flows. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## UDP Broadcasting Meets the More Focused Multicasting

DevFeed: [UDP Broadcasting Meets the More Focused Multicasting](<https://devfeed.tech/articles/udp-broadcasting-meets-the-more-focused-multicasting-123906.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/09/udp-broadcasting-meets-the-more-focused-multicasting/>)

Author: Maya Posch

Published: 2026-11-09T18:00:41Z

Content type: article

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [broadcasting](<https://devfeed.tech/tags/broadcasting.md>), [comparisons](<https://devfeed.tech/tags/comparisons.md>), [hackaday-columns](<https://devfeed.tech/tags/hackaday-columns.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [multicast](<https://devfeed.tech/tags/multicast.md>), [network-hacks](<https://devfeed.tech/tags/network-hacks.md>), [networking](<https://devfeed.tech/tags/networking.md>), [subnets](<https://devfeed.tech/tags/subnets.md>), [udp](<https://devfeed.tech/tags/udp.md>)

### AI overview

IPv4 UDP service discovery has three options in the article: send to an interface's directed broadcast address, use 255.255.255.255, or multicast to 224.0.0.1, which is intended to reach all nodes on the local network without router forwarding. Directed broadcast is the author's tentative preference because it identifies the interface used and can simplify sorting responses; the text cautions that determining an interface's broadcast address may be unreliable, with a Poco fix expected in version 1.16.0 and a workaround available. The all-nodes multicast option depends on IGMP being supported and working correctly. The author finds no clearly best choice and presents IPv4's alternatives as carrying different complications, while noting IPv6 uses link-local multicast in place of broadcast.

### Source excerpt

After previously exploring the basics of UDP broadcasting, why IPv4 subnets are an exciting feature that you really want to dive into, as well as the contentious topic of IPv6, ...read more

## CVE-2026-123576 - Hickory DNS 0.24.0 through 0.26.1 Memory Exhaustion via DNS-over-QUIC Requests

DevFeed: [CVE-2026-123576 - Hickory DNS 0.24.0 through 0.26.1 Memory Exhaustion via DNS-over-QUIC Requests](<https://devfeed.tech/articles/cve-2026-123576-hickory-dns-0-24-0-through-0-26-1-memory-exhaustion-via-dns-over-quic-requests-122350.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-123576>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-08T02:16:50Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123576](<https://devfeed.tech/tags/cve-2026-123576.md>), [dns](<https://devfeed.tech/tags/dns.md>), [memory](<https://devfeed.tech/tags/memory.md>), [quic](<https://devfeed.tech/tags/quic.md>)

### AI overview

Hickory DNS versions 0.24.0 through 0.26.1 are described as vulnerable to remote memory exhaustion through DNS-over-QUIC. An attacker can open many connections and send incomplete requests containing large length prefixes; the server's pre-allocated buffers may persist without a timeout, consuming memory. The excerpt provides no remediation or mitigation details.

### Source excerpt

CVE ID :CVE-2026-123576 Published : Nov. 8, 2026, 2:16 a.m. | 47 minutes ago Description :Hickory DNS 0.24.0 through 0.26.1 contains a memory exhaustion vulnerability that allows remote attackers to consume server resources by sending incomplete DNS-over-QUIC request bodies. Attackers can open many connections and send only large length prefixes, causing pre-allocated buffers to persist without timeout and exhausting server memory. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## The Split Protocol Decides the Result: Re-Evaluating Encrypted Traffic Classification

DevFeed: [The Split Protocol Decides the Result: Re-Evaluating Encrypted Traffic Classification](<https://devfeed.tech/articles/the-split-protocol-decides-the-result-re-evaluating-encrypted-traffic-classification-118444.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06290>)

Author: Mayan Sharma, Kriti Saini, Devansh Behl

Published: 2026-11-05T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [few-shot](<https://devfeed.tech/topics/few-shot.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [classification](<https://devfeed.tech/tags/classification.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [encrypted-traffic](<https://devfeed.tech/tags/encrypted-traffic.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [gradient-boosted-trees](<https://devfeed.tech/tags/gradient-boosted-trees.md>), [quic](<https://devfeed.tech/tags/quic.md>)

### AI overview

Encrypted traffic classification scores can change sharply with the data split: on one public corpus, the same model and code achieved macro-F1 0.992 under a literature-standard protocol and 0.567 when flows from each packet capture stayed together. On a month of backbone QUIC traffic, server-disjoint splitting reduced macro-F1 by 0.192, while random, temporal and client-disjoint results were statistically indistinguishable from session-disjoint results. The authors propose single-identifier probes to identify leakage: a tree using only capture IDs scored 0.983 with a random split and 0.000 with session-disjoint splitting. A metric-trained embedding led four deep baselines but did not surpass gradient-boosted trees using twenty packet sizes. Distance-based unknown-app rejection beat softmax thresholding, yet removing metric objectives improved rejection; five labeled flows per class recovered 91% of the cross-corpus zero-shot transfer deficit. The abstract reports results from two public corpora and backbone QUIC traffic.

### Source excerpt

arXiv:2611.06290v1 Announce Type: cross Abstract: Encrypted traffic classifiers are routinely reported at 95-99% accuracy. We show that on one of two public corpora, the same model and code score macro-F1 0.992 under the evaluation protocol standard in the literature and 0.567 under a protocol that keeps flows from one packet capture on one side of the split. Nothing changes but the partition (gap 0.426 over eight seeds, p = 0.008 after Holm-Bonferroni correction). The inflation is not a property of random splitting as such. On a month of backbone QUIC traffic, we evaluate five split protocols at eight seeds each: random, temporal and client-disjoint splitting are statistically indistinguishable from session-disjoint, while server-disjoint splitting costs 0.192 macro-F1 (d = 17.0, p = 0.008). Which axis matters depends on how the corpus was collected, in a way invisible from its label space. We give a diagnostic that identifies the right axis before any model is trained: single-identifier probes. A decision tree on the capture identifier alone reaches 0.983 under a random split and exactly 0.000 under session-disjoint splitting. Under this evaluation, a metric-trained flow embedding leads four deep baselines but does not beat gradient-boosted trees on twenty packet sizes. Five of our own pre-registered architectural claims fail: distance-based rejection of unknown applications beats softmax thresholding, but ablating every metric objective makes rejection better, because class separation correlates at r = -0.88 with rejection quality. Few-shot enrollment is flat within a corpus but, across corpora, five labelled flows per class recover 91% of the deficit left by failed zero-shot transfer. All splits, results, code and negative findings are released.

## Accelerating QUIC Encryption in WebAssembly Using WASM-SIMD

DevFeed: [Accelerating QUIC Encryption in WebAssembly Using WASM-SIMD](<https://devfeed.tech/articles/accelerating-quic-encryption-in-webassembly-using-wasm-simd-113868.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01989>)

Author: Sota Yamawaki, Yasuo Okabe

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [vectorization techniques](<https://devfeed.tech/topics/vectorization-techniques.md>)

Tags: [acceleration](<https://devfeed.tech/tags/acceleration.md>), [aes](<https://devfeed.tech/tags/aes.md>), [amdahl-s-law](<https://devfeed.tech/tags/amdahl-s-law.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [edge](<https://devfeed.tech/tags/edge.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [gigabit-ethernet](<https://devfeed.tech/tags/gigabit-ethernet.md>), [limits](<https://devfeed.tech/tags/limits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [native](<https://devfeed.tech/tags/native.md>), [network](<https://devfeed.tech/tags/network.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [quic](<https://devfeed.tech/tags/quic.md>), [simd](<https://devfeed.tech/tags/simd.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Explicit WASM-SIMD kernels substantially improve QUIC encryption performance in WebAssembly, but shift the main limits to other parts of the stack. On two hosts connected by 10-Gigabit Ethernet, kernels processing eight AES blocks or four ChaCha20 blocks per pass increased receiver goodput over a non-SIMD baseline by 61.34% for AES-128-GCM and 31.55% for ChaCha20-Poly1305; compiler auto-vectorization improved AES-128-GCM by only 1.28%. ChaCha20-Poly1305 achieved 1.99 times the goodput of AES-128-GCM. Profiling and Amdahl's law suggest that even native-speed cryptography would leave the Wasm stack at roughly one third the goodput of the fastest native stack. Memory allocation, runtime overhead, and per-datagram UDP I/O remain constraints, so cryptographic acceleration alone is insufficient.

### Source excerpt

arXiv:2611.01989v1 Announce Type: cross Abstract: WebAssembly (Wasm) runs untrusted code in a portable, lightweight sandbox and is increasingly used to host services on shared servers and edge platforms. Running the QUIC transport protocol inside Wasm would let each application choose and update its own transport without changing the host. QUIC, however, encrypts every packet, and Wasm offers neither dedicated AES instructions nor carry-less multiplication; a Wasm QUIC stack has been reported to reach only 17.6% of native goodput, with cryptography as its largest cost. Whether the 128-bit SIMD extension of Wasm (WASM-SIMD) can recover this cost, and what limits a pure-Wasm stack once it does, has remained unclear. Here we show that explicit WASM-SIMD kernels recover much of the cryptographic cost, after which non-cryptographic costs become the limit. On two hosts connected by 10-Gigabit Ethernet, kernels that process eight AES blocks or four ChaCha20 blocks per pass raise receiver goodput over a non-SIMD baseline by 61.34% for AES-128-GCM and 31.55% for ChaCha20-Poly1305, whereas compiler auto-vectorization gains only 1.28% for AES-128-GCM. ChaCha20-Poly1305 still delivers 1.99 times the goodput of AES-128-GCM, confirming end to end the preference that stand-alone cipher benchmarks suggest. Receiver-side profiling combined with Amdahl's law predicts that even native-speed cryptography would leave Wasm at roughly one third of the goodput of the fastest native stack. Cryptographic acceleration is therefore necessary but not sufficient: memory allocation, runtime overhead and per-datagram UDP I/O now bound pure-Wasm transports. We anticipate that this per-category cost breakdown will guide further optimization of Wasm network stacks and the design of system interfaces for batched I/O.

## P99 CONF 2026 Recap: A Tail of Two Days

DevFeed: [P99 CONF 2026 Recap: A Tail of Two Days](<https://devfeed.tech/articles/p99-conf-2026-recap-a-tail-of-two-days-102608.md>)

Original publisher: [Read original article](<https://www.scylladb.com/2026/10/27/p99-conf-2026-recap/>)

Author: Cynthia Dunlop

Published: 2026-10-27T15:53:35Z

Content type: article

Language: en

Sources: [ScyllaDB](<https://devfeed.tech/sources/scylladb.md>)

Topics: [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [arrow](<https://devfeed.tech/tags/arrow.md>), [asia-pacific](<https://devfeed.tech/tags/asia-pacific.md>), [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [avi](<https://devfeed.tech/tags/avi.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azul](<https://devfeed.tech/tags/azul.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [p99-conf](<https://devfeed.tech/tags/p99-conf.md>), [recap](<https://devfeed.tech/tags/recap.md>)

### AI overview

P99 CONF 2026 kept its focus on tail latency while adding a dedicated Europe/India/Asia-Pacific track and featuring AI in roughly a dozen of its 60-plus talks. The recap highlights practical agent work, including Netflix's autonomous agent tracing inefficiencies in live services and proposing fixes, and a Redis experiment giving an agent a multicore cluster, profiles, MCP access and a budget to run performance tests. Other talks covered async I/O, databases, vector search, observability, networking and sandboxes. One reported performance comparison: TigerBeetle's Zig object-storage client, built with custom DNS, TLS, HTTP, single-threading, zero-copy and io_uring, was said to be 10 times faster than the AWS and GCP SDKs. The conference's pre-recorded talks with live audience chat are available on demand.

### Source excerpt

Our Aussie host's take on P99 CONF around the clock and (now) anytime on demand

## Embedding Large PQC KEMs in IKEv2

DevFeed: [Embedding Large PQC KEMs in IKEv2](<https://devfeed.tech/articles/embedding-large-pqc-kems-in-ikev2-100289.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.32356>)

Author: Daniel Herzinger, Marco Thomas, Tobias Handirk, Stefan-Lukas Gazdag, Daniel Loebenberger, Marian Margraf

Published: 2026-10-26T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [compatibility](<https://devfeed.tech/tags/compatibility.md>), [computer](<https://devfeed.tech/tags/computer.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [data](<https://devfeed.tech/tags/data.md>), [error-correcting-codes](<https://devfeed.tech/tags/error-correcting-codes.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [handshake](<https://devfeed.tech/tags/handshake.md>), [handshakes](<https://devfeed.tech/tags/handshakes.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [key](<https://devfeed.tech/tags/key.md>), [keys](<https://devfeed.tech/tags/keys.md>), [measurements](<https://devfeed.tech/tags/measurements.md>), [ml-kem](<https://devfeed.tech/tags/ml-kem.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [performance](<https://devfeed.tech/tags/performance.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [quic](<https://devfeed.tech/tags/quic.md>), [size](<https://devfeed.tech/tags/size.md>), [specification](<https://devfeed.tech/tags/specification.md>), [transport](<https://devfeed.tech/tags/transport.md>)

### AI overview

The study compares eight ways to carry large post-quantum KEM keys in IKEv2, implemented on one open-source codebase and tested in 126,500 handshakes across 1,296 configurations. No approach fully offsets the key-size impact. Under challenging conditions, none handles Classic McEliece acceptably: approaches either congest the link or average nearly two minutes per handshake. For ML-KEM and FrodoKEM, the authors identify two paths: standardized IKEv2 extensions, which preserve compatibility but require larger implementation changes and further optimization, or delegating transport to QUIC. The latter can avoid those drawbacks through a composite key exchange; QUIKE-composite had the best overall performance. These findings reflect the tested bandwidth, latency, loss, and KEM configurations.

### Source excerpt

arXiv:2610.32356v1 Announce Type: new Abstract: Post-quantum key encapsulation mechanisms carry public keys far larger than the established VPN handshake protocol IKEv2 was designed for. At the same time, its initial exchange comprising the public keys cannot be fragmented. In response, the IETF discusses a range of protocol adjustments, yet these proposals have never been compared in terms of their performance and stability under identical conditions. We systematically screened the IETF document corpus for such proposals, added three of our own (one using forward error correction and two using IKEv2 with QUIC, namely QUIKE and QUIKE with a composite key exchange), identified two specification gaps in existing acknowledgment drafts, and implemented all eight on the same open-source codebase. Measurements across different bandwidths, latencies, and packet loss rates, and with ML-KEM, FrodoKEM, and Classic McEliece, total 126 500 handshakes in 1296 different configurations and show that no mechanism fully compensates for the effect of the key size on performance. For Classic McEliece, no approach handles challenging conditions acceptably. The approaches either congest the link or take up to nearly two minutes per handshake on average. For ML-KEM and FrodoKEM, there are two ways forward: building on already standardized extensions or delegating the transport. The former requires the larger implementation change and needs further optimization, such as acknowledgment mechanisms or error-correcting codes, but grants continuity and compatibility. The latter can use a composite key exchange to avoid these drawbacks and achieve a faster, more resilient handshake and leaner implementation, with QUIKE-composite offering the best overall performance.

## Securing autonomous fleet communications at scale with mTLS over QUIC using Network Load Balancer passthrough

DevFeed: [Securing autonomous fleet communications at scale with mTLS over QUIC using Network Load Balancer passthrough](<https://devfeed.tech/articles/securing-autonomous-fleet-communications-at-scale-with-mtls-over-quic-using-network-load-balancer-passthrough-97734.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/securing-autonomous-fleet-communications-at-scale-with-mtls-over-quic-using-network-load-balancer-passthrough/>)

Author: Priya Huddar

Published: 2026-10-23T17:15:39Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [autonomous vehicles](<https://devfeed.tech/topics/autonomous-vehicles.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-drones](<https://devfeed.tech/tags/autonomous-drones.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [communications](<https://devfeed.tech/tags/communications.md>), [controller](<https://devfeed.tech/tags/controller.md>), [device](<https://devfeed.tech/tags/device.md>), [drones](<https://devfeed.tech/tags/drones.md>), [eks](<https://devfeed.tech/tags/eks.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [latency](<https://devfeed.tech/tags/latency.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [passthrough](<https://devfeed.tech/tags/passthrough.md>), [pods](<https://devfeed.tech/tags/pods.md>), [quic](<https://devfeed.tech/tags/quic.md>), [scale](<https://devfeed.tech/tags/scale.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article's reference setup keeps QUIC's TLS 1.3 handshake on the application pods while an AWS Network Load Balancer forwards QUIC packets and routes sessions by Server ID embedded in Connection IDs. On Amazon EKS, the AWS Load Balancer Controller provisions the QUIC-enabled NLB; quic-go pods use unique injected Server IDs and AWS Private CA certificates to verify each device with mTLS. The walkthrough covers cluster and controller setup, certificate provisioning, baseline server-only TLS verification, then requiring and testing client certificates. A valid trusted certificate succeeds; missing or untrusted certificates fail during the handshake. A critical constraint is the exact 17-byte destination Connection ID required for non-Envoy servers: incorrect length can stall mTLS handshakes when certificate data arrives in separate Handshake packets. The article also notes that the NLB uses TCP health checks and does not drain QUIC connections; target replacement can break in-flight sessions, so clients need reconnect handling.

### Source excerpt

Learn how to architect end-to-end mutual TLS (mTLS) authentication over QUIC using AWS Network Load Balancer passthrough mode. This post shows how to route QUIC traffic to quic-go server pods on Amazon EKS through the AWS Load Balancer Controller, with per-device certificate authentication for latency-sensitive fleet workloads such as autonomous drones.

## Shipping Media Over QUIC at Meta Scale for Instagram Live Ingest

DevFeed: [Shipping Media Over QUIC at Meta Scale for Instagram Live Ingest](<https://devfeed.tech/articles/shipping-media-over-quic-at-meta-scale-for-instagram-live-ingest-85619.md>)

Original publisher: [Read original article](<https://engineering.fb.com/2026/10/12/video-engineering/shipping-media-over-quic-at-meta-scale-for-instagram-live-ingest/>)

Author: Konstantin Tsoy; Aman Sharma; Hari Anil Kumar; Alan Frindell; Sandarsh Srivastava

Published: 2026-10-12T16:01:32Z

Content type: article

Language: en

Sources: [Engineering at Meta](<https://devfeed.tech/sources/engineering-at-meta.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [data-infrastructure](<https://devfeed.tech/tags/data-infrastructure.md>), [instagram](<https://devfeed.tech/tags/instagram.md>), [ios](<https://devfeed.tech/tags/ios.md>), [meta](<https://devfeed.tech/tags/meta.md>), [networking-traffic](<https://devfeed.tech/tags/networking-traffic.md>), [quic](<https://devfeed.tech/tags/quic.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [streaming-video](<https://devfeed.tech/tags/streaming-video.md>), [video](<https://devfeed.tech/tags/video.md>), [video-engineering](<https://devfeed.tech/tags/video-engineering.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Meta describes deploying Media over QUIC (MoQ) for Instagram Live video ingest on iOS and Android. The rollout matched the existing RUSH protocol on streaming quality and reliability measures, and Meta plans to explore broader live video delivery and playback uses.

### Source excerpt

Meta has begun deploying Media over QUIC (MoQ), an emerging open protocol for real-time video streaming at scale. MoQ will help simplify our protocol stack for live streaming video and enhance overall user experience for live video. We're sharing how we shipped MoQ on Instagram Live ingest, and what the future looks like from here. [...] Read More... The post Shipping Media Over QUIC at Meta Scale for Instagram Live Ingest appeared first on Engineering at Meta.

## We View Consumer Data as Toxic Waste

DevFeed: [We View Consumer Data as Toxic Waste](<https://devfeed.tech/articles/we-view-consumer-data-as-toxic-waste-64355.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17484548/obscura-carl-dong>)

Author: Abhishek Prakash

Published: 2026-10-03T07:47:16Z

Content type: opinion

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [Security](<https://devfeed.tech/topics/security.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>)

Tags: [bitcoin](<https://devfeed.tech/tags/bitcoin.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [data](<https://devfeed.tech/tags/data.md>), [interview](<https://devfeed.tech/tags/interview.md>), [logs](<https://devfeed.tech/tags/logs.md>), [obscura-vpn](<https://devfeed.tech/tags/obscura-vpn.md>), [quic](<https://devfeed.tech/tags/quic.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [trust](<https://devfeed.tech/tags/trust.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

Obscura VPN separates identity from browsing through a two-company relay: its first hop can see the connecting IP but relays traffic encrypted to keys controlled by Mullvad, whose exit servers do not see the user's identity or payment information. The founder says privacy correlation remains blocked as long as either company is uncompromised, while acknowledging the companies could both be compromised. The client uses QUIC, which the founder says resembles HTTP/3 and makes censorship inspection more costly, and the company accepts account-number login without email, plus Monero and Bitcoin over Lightning. The open-source client has an Android reproducible-build prototype; other platforms are still being pursued. The excerpt says users can inspect code and compare the exit-hop key with Mullvad's published list. Obscura still sees connecting IPs, and its service is priced at $8 per month.

### Source excerpt

Obscura VPN splits your identity from your browsing across two independent companies so neither can see both. Founder Carl Dong on trust, QUIC, reproducible builds, and why the no-logs promise stopped being enough.

## Burp Suite Adds HTTP/3 Support and High-Throughput Fuzzing Techniques

DevFeed: [Burp Suite Adds HTTP/3 Support and High-Throughput Fuzzing Techniques](<https://devfeed.tech/articles/http-3-in-burp-suite-it-s-time-to-find-a-bigger-wordlist-58937.md>)

Original publisher: [Read original article](<https://portswigger.net/research/http3-in-burp-suite>)

Author: Tom Stacey

Published: 2026-09-23T14:00:00Z

Content type: release

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [race-condition](<https://devfeed.tech/topics/race-condition.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [http3](<https://devfeed.tech/tags/http3.md>), [network](<https://devfeed.tech/tags/network.md>), [quic](<https://devfeed.tech/tags/quic.md>), [race-condition](<https://devfeed.tech/tags/race-condition.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

PortSwigger announces HTTP/3 support in Burp Suite through a new HTTP/3 Adapter plugin and HTTP/3 support in Turbo Intruder. The article describes performance tuning, high request rates, and new race-condition testing techniques over HTTP/3.

### Source excerpt

How many bugs have you missed because you didn't send quite enough HTTP requests? Turbo Intruder now supports HTTP/3, can comfortably exceed 100,000 requests per second over Wi-Fi, and auto-tunes for

## Obscura VPN now offers a desktop app for Linux

DevFeed: [Obscura VPN now offers a desktop app for Linux](<https://devfeed.tech/articles/obscura-vpn-now-offers-a-desktop-app-for-linux-58284.md>)

Original publisher: [Read original article](<https://www.omgubuntu.co.uk/2026/09/obscura-vpn-linux-app>)

Author: Joey Sneddon

Published: 2026-09-22T16:50:42Z

Content type: news

Language: en

Sources: [OMG! Ubuntu](<https://devfeed.tech/sources/omg-ubuntu.md>)

Topics: [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Network](<https://devfeed.tech/topics/network.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [desktop](<https://devfeed.tech/tags/desktop.md>), [gplv3](<https://devfeed.tech/tags/gplv3.md>), [linux](<https://devfeed.tech/tags/linux.md>), [news](<https://devfeed.tech/tags/news.md>), [obscura-vpn](<https://devfeed.tech/tags/obscura-vpn.md>), [privacy-tools](<https://devfeed.tech/tags/privacy-tools.md>), [quic](<https://devfeed.tech/tags/quic.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

Obscura VPN has launched a native Linux desktop app with two-step routing through Obscura and Mullvad, plus a QUIC-based stealth protocol intended to disguise VPN traffic as HTTP/3 browsing. The app supports Ubuntu and other distributions on Intel and AMD devices, and its code is now GPLv3 licensed.

### Source excerpt

Obscura VPN has launched a native Linux app, giving desktop users an easier way to access it (without wrangling Wireguard configuration files). Linux isn't short of VPN providers, but Obscura, founded by former Bitcoin Core contributor Carl Dong, has a different pitch to most. Rather than your traffic being routed through a single provider, Obscura VPN uses a two-step relay: it acts as the 'entry node' (seeing your original IP address) while another VPN provider, Mullvad, acts as the 'exit node' (the websites you visit). Obscura's Linux app also supports the QUIC-based stealth protocol, which disguises your VPN connection as [...] You're reading Obscura VPN now offers a desktop app for Linux, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

## Helidon 27 Released

DevFeed: [Helidon 27 Released](<https://devfeed.tech/articles/helidon-27-released-57766.md>)

Original publisher: [Read original article](<https://inside.java/2026/09/22/helidon27-release/>)

Author: Ali Mukadam (Helidon)

Published: 2026-09-22T00:00:00Z

Content type: release

Language: en

Sources: [Inside Java](<https://devfeed.tech/sources/inside-java.md>)

Topics: [project release](<https://devfeed.tech/topics/project-release.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [version](<https://devfeed.tech/topics/version.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [observability](<https://devfeed.tech/topics/observability.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [helidon](<https://devfeed.tech/tags/helidon.md>), [helidon-27-released](<https://devfeed.tech/tags/helidon-27-released.md>), [jdk-27](<https://devfeed.tech/tags/jdk-27.md>), [model](<https://devfeed.tech/tags/model.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Helidon 27 is the first Tip release, tracks JDK 27, and targets teams seeking newer Java and Helidon features; Helidon 4.5 remains the LTS Tail for longer validation and production-support needs. Non-LTS releases receive fixes until the next Tip; LTS support extends to one year after the following LTS, typically about three years. Declarative API coverage now includes gRPC, Messaging, GraphQL, and OpenAPI, but remains Preview until Helidon 29 LTS. New Helidon Messaging uses ordinary blocking Java methods and logical channels, with pluggable connectors and configuration separating business code from Kafka, JMS, or Pulsar transport details; it is Preview. Helidon Data JDBC lets developers write repository SQL directly while Helidon generates JDBC plumbing at build time; it is Incubating and omits ORM features such as dirty checking and lazy loading. The release also moves Helidon Core context handling from ThreadLocal to JDK ScopedValue without changing the public Context API.

### Source excerpt

The Helidon team is pleased to announce Helidon 27, the first release under the Tip-and-Tail model used by OpenJDK.

## Apache Announces Iggy Streaming Platform and Sourcelume AI Training-Data Provenance Project as Top-Level Projects

DevFeed: [Apache Announces Iggy Streaming Platform and Sourcelume AI Training-Data Provenance Project as Top-Level Projects](<https://devfeed.tech/articles/the-apache-software-foundation-announces-new-top-level-projects-50269.md>)

Original publisher: [Read original article](<https://news.apache.org/foundation/entry/the-apache-software-foundation-announces-new-top-level-projects-6>)

Author: The ASF

Published: 2026-08-27T13:00:00Z

Content type: release

Language: en

Sources: [The ASF Blog](<https://devfeed.tech/sources/the-asf-blog.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [io\_uring](<https://devfeed.tech/topics/io-uring.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Training AI Models](<https://devfeed.tech/topics/training-ai-models.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apache](<https://devfeed.tech/tags/apache.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [blog](<https://devfeed.tech/tags/blog.md>), [building](<https://devfeed.tech/tags/building.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [post](<https://devfeed.tech/tags/post.md>), [press-releases](<https://devfeed.tech/tags/press-releases.md>), [projects](<https://devfeed.tech/tags/projects.md>), [published](<https://devfeed.tech/tags/published.md>), [rust](<https://devfeed.tech/tags/rust.md>), [software](<https://devfeed.tech/tags/software.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [top](<https://devfeed.tech/tags/top.md>), [training](<https://devfeed.tech/tags/training.md>), [training-data](<https://devfeed.tech/tags/training-data.md>)

### AI overview

The Apache Software Foundation announced that Apache Iggy, a Rust-based persistent message streaming platform, and Apache Sourcelume, open-source instrumentation for AI training-data provenance, became Apache Top-Level Projects.

### Source excerpt

Introducing Apache Iggy™, a persistent message streaming platform written in Rust, and Apache Sourcelume, open source instrumentation for AI training-data provenance Wilmington, DE - August 27, 2026 - The Apache Software Foundation (ASF), the global home of open source software the world relies on, today announced that Apache Iggy and Apache Sourcelume have become Top-Level [...] The post The Apache® Software Foundation Announces New Top-Level Projects appeared first on The ASF Blog.

## HTTP/1.1 workarounds: sharding, sprites, and bundling

DevFeed: [HTTP/1.1 workarounds: sharding, sprites, and bundling](<https://devfeed.tech/articles/http-1-1-workarounds-sharding-sprites-and-bundling-89133.md>)

Original publisher: [Read original article](<https://specification.website/spec/performance/http1-workarounds/>)

Author: Joost de Valk

Published: 2026-06-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [sharding](<https://devfeed.tech/topics/sharding.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [avoid](<https://devfeed.tech/tags/avoid.md>), [compression](<https://devfeed.tech/tags/compression.md>), [http](<https://devfeed.tech/tags/http.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [performance](<https://devfeed.tech/tags/performance.md>), [sharding](<https://devfeed.tech/tags/sharding.md>)

### AI overview

Domain sharding and image sprites were workarounds for HTTP/1.1's connection limit, but they can undermine performance with HTTP/2 and HTTP/3. The article recommends removing them and treating bundling as a tradeoff: bundle resources to improve compression while splitting code when caching or unused routes make a larger bundle costly.

### Source excerpt

Domain sharding and image sprites were workarounds for HTTP/1.1's connection limit; under HTTP/2 and HTTP/3 they hurt -- drop them. Bundling is the nuanced one: stop concatenating to cut requests, start doing it to cut bytes.

## HTTP/2 and HTTP/3

DevFeed: [HTTP/2 and HTTP/3](<https://devfeed.tech/articles/http-2-and-http-3-89134.md>)

Original publisher: [Read original article](<https://specification.website/spec/performance/http3/>)

Author: Joost de Valk

Published: 2026-06-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [devtools](<https://devfeed.tech/tags/devtools.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [performance](<https://devfeed.tech/tags/performance.md>), [quic](<https://devfeed.tech/tags/quic.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [tcp-handshake](<https://devfeed.tech/tags/tcp-handshake.md>)

### AI overview

This tutorial compares HTTP/1.1, HTTP/2, and HTTP/3, explaining how HTTP/3 uses QUIC to reduce transport-level blocking and support connection migration. It gives deployment guidance for enabling HTTP/3 at a CDN edge, requiring TLS 1.3, reviewing HTTP/1.1-era optimizations, and verifying protocol support.

### Source excerpt

Serve over HTTP/2 at minimum and HTTP/3 where you can. Multiplexing eliminates head-of-line blocking; QUIC removes TCP handshake delays.

## Bun v1.3.14

DevFeed: [Bun v1.3.14](<https://devfeed.tech/articles/bun-v1-3-14-49453.md>)

Original publisher: [Read original article](<https://bun.com/blog/bun-v1.3.14>)

Author: Jarred Sumner

Published: 2026-05-13T03:19:35Z

Content type: release

Language: en

Sources: [Bun](<https://devfeed.tech/sources/bun-com.md>)

Topics: [Bun](<https://devfeed.tech/topics/bun.md>), [Image processing](<https://devfeed.tech/topics/image-processing.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [linker](<https://devfeed.tech/topics/linker.md>), [builds](<https://devfeed.tech/topics/builds.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [macOS](<https://devfeed.tech/topics/macos.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bun](<https://devfeed.tech/tags/bun.md>), [cache](<https://devfeed.tech/tags/cache.md>), [fetch](<https://devfeed.tech/tags/fetch.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [image-processing](<https://devfeed.tech/tags/image-processing.md>), [linker](<https://devfeed.tech/tags/linker.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [quic](<https://devfeed.tech/tags/quic.md>)

### AI overview

Bun v1.3.14 introduces a built-in image-processing API with support for common image formats and chainable transformations. It also adds an experimental global virtual store for faster warm installs, experimental HTTP/2 and HTTP/3 clients, HTTP/3 support in Bun.serve(), platform builds, and numerous fixes and compatibility improvements.

### Source excerpt

Fixes 92 issues (addressing 380 👍). Bun.Image -- a built-in image processing API, 7x faster warm installs with the isolated linker's global store, experimental HTTP/2 and HTTP/3 clients for fetch(), HTTP/3 (QUIC) in Bun.serve(), rewritten fs.watch() on Linux and macOS, --no-orphans CLI flag, process.execve(), Bun.Terminal on Windows via ConPTY, FreeBSD and Android builds, shared SSL_CTX cache, smaller binaries, and many bugfixes and Node.js compatibility improvements.

## Post-Quantum Cryptography Proof of Concept Implementations

DevFeed: [Post-Quantum Cryptography Proof of Concept Implementations](<https://devfeed.tech/articles/post-quantum-cryptography-proof-of-concept-implementations-30238.md>)

Original publisher: [Read original article](<https://www.netmeister.org/blog/pqc-pocs.html>)

Published: 2025-07-20T21:35:33Z

Content type: tutorial

Language: en

Sources: [Signs of Triviality](<https://devfeed.tech/sources/signs-of-triviality.md>)

Topics: [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Server](<https://devfeed.tech/topics/server.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [language](<https://devfeed.tech/tags/language.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [post-quantum-cryptography](<https://devfeed.tech/tags/post-quantum-cryptography.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [quic](<https://devfeed.tech/tags/quic.md>), [server](<https://devfeed.tech/tags/server.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

The article presents a few QUIC post-quantum cryptography TLS server implementations intended to help verify client and language capabilities.

### Source excerpt

A few quic PQC TLS server implekentations to help you verify client and language capabilities.

## Making Chrome QUICer

DevFeed: [Making Chrome QUICer](<https://devfeed.tech/articles/making-chrome-quicer-4191.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2024/12/making-chrome-quicer.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2024-12-17T18:09:00Z

Content type: article

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [dns](<https://devfeed.tech/tags/dns.md>), [google](<https://devfeed.tech/tags/google.md>), [google-search](<https://devfeed.tech/tags/google-search.md>), [handshake](<https://devfeed.tech/tags/handshake.md>), [http](<https://devfeed.tech/tags/http.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [ip](<https://devfeed.tech/tags/ip.md>), [latency](<https://devfeed.tech/tags/latency.md>), [lookup](<https://devfeed.tech/tags/lookup.md>), [memory](<https://devfeed.tech/tags/memory.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [none](<https://devfeed.tech/tags/none.md>), [october](<https://devfeed.tech/tags/october.md>), [optimizing](<https://devfeed.tech/tags/optimizing.md>), [packets](<https://devfeed.tech/tags/packets.md>)

### AI overview

Chrome enabled HTTP/3's ORIGIN frame and Server's Preferred Address by default in M131 to improve connection reuse and reduce round-trip time. ORIGIN lets a server specify which domains may share a connection, avoiding extra DNS checks and new connections when IP addresses mismatch; Chrome metrics suggest nearly 20% of HTTP/3 connections would otherwise be unnecessary because of such mismatches. New connections can add DNS, handshake, cryptographic, CPU and memory costs, and 0-RTT may fail or be unavailable for non-safe requests. Server's Preferred Address lets the server, after handshake confirmation, suggest a different IP for the client to migrate to, potentially bypassing a load balancer or a longer Anycast route. Chrome tests reported migration success above 99% and average RTT reductions of 40-80%. The excerpt says Google's Media CDN was the only service widely advertising an alternative address so far.

### Source excerpt

In October 2020, Chrome enabled HTTP/3 by default. HTTP/3 (RFC 9114) runs over IETF QUIC (RFC9000). Default-enabling HTTP/3 in Chrome resulted in improved performance compared not only HTTP/1 and HTTP/2, but also Google QUIC. Benefits included reduced Google search latency and fewer rebuffers for YouTube. The journey to optimizing performance did not end when HTTP/3 was default enabled. Recent advancements include the implementation of the HTTP/3 ORIGIN frame (RFC 9412) and Server's Preferred Address (RFC 9000 Section 9.6). The former enhances connection coalescing, while the latter reduces a connection's round trip time (RTT). Both features have been enabled by default in M131, which was released to Stable on 11/19. ORIGIN Frame When a connection is established for a specific hostname, the server's certificate typically contains numerous other hostnames for which the server is authoritative. However, a client cannot immediately send requests for those other hostnames on that connection without first performing a DNS lookup for the other hostname and verifying that the IP address of the connection matches the resolved address. This additional DNS resolution introduces latency and significantly reduces the likelihood of connection pooling due to potential IP mismatches. The metrics from Chrome indicate that nearly 20% of HTTP/3 connections would be unnecessary if not for this IP mismatch. Creating a new connection, even with QUIC 0-RTT, is expensive in terms of latency, memory, and CPU usage. This is because: DNS resolution adds latency unless cached locally in Chrome's DNS cache. Both client and server must send multiple packets to complete a QUIC handshake. TLS necessitates CPU-intensive asymmetric cryptography on both ends. The congestion controller begins in its default state, potentially leading to under or over-sending. 0-RTT might fail. Non-safe requests aren't sent via 0-RTT. More connections consume more memory. Additionally, features like HTTP priorities (R

## Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy

DevFeed: [Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy](<https://devfeed.tech/articles/rock-and-rollback-realtime-multiplayer-in-the-browser-with-rust-and-bevy-25823.md>)

Original publisher: [Read original article](<https://www.metabrew.com/article/rock-and-rollback-realtime-multiplayer-games-with-bevy>)

Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil}

Published: 2024-12-08T06:00:00Z

Content type: tutorial

Language: en

Sources: [Richard Jones](<https://devfeed.tech/sources/richard-jones.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [browser-game](<https://devfeed.tech/topics/browser-game.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Bevy](<https://devfeed.tech/topics/bevy.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [WebRTC](<https://devfeed.tech/topics/webrtc.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>)

Tags: [bevy](<https://devfeed.tech/tags/bevy.md>), [bevygap](<https://devfeed.tech/tags/bevygap.md>), [browser](<https://devfeed.tech/tags/browser.md>), [gamedev](<https://devfeed.tech/tags/gamedev.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [multiplayer](<https://devfeed.tech/tags/multiplayer.md>), [netcode](<https://devfeed.tech/tags/netcode.md>), [quic](<https://devfeed.tech/tags/quic.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [rust](<https://devfeed.tech/tags/rust.md>), [snapshots](<https://devfeed.tech/tags/snapshots.md>), [udp](<https://devfeed.tech/tags/udp.md>), [webrtc](<https://devfeed.tech/tags/webrtc.md>)

### AI overview

This article discusses building a realtime multiplayer browser game with Rust and Bevy. It explains why TCP can delay updates, considers WebRTC and WebTransport over HTTP/3 and QUIC for unreliable data channels, and introduces snapshot interpolation as a multiplayer networking model.

### Source excerpt

How hard it is to build a realtime multiplayer browser game? Like asteroids, but multiplayer. Retro vibes with modern netcode 🚀.

## Next level customer experience with HTTP/3 traffic engineering

DevFeed: [Next level customer experience with HTTP/3 traffic engineering](<https://devfeed.tech/articles/next-level-customer-experience-with-http-3-traffic-engineering-47475.md>)

Original publisher: [Read original article](<https://engineering.zalando.com/posts/2024/06/next-level-customer-experience-with-http3-traffic-engineering.html>)

Author: Dmitry Kolesnikov

Published: 2024-06-17T22:00:00Z

Content type: article

Language: en

Sources: [Zalando](<https://devfeed.tech/sources/zalando-engineering-blog.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [Network](<https://devfeed.tech/topics/network.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [protocols](<https://devfeed.tech/topics/protocols.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [http](<https://devfeed.tech/tags/http.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [quic](<https://devfeed.tech/tags/quic.md>), [reduction](<https://devfeed.tech/tags/reduction.md>), [traffic-engineering](<https://devfeed.tech/tags/traffic-engineering.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [zalando](<https://devfeed.tech/tags/zalando.md>)

### AI overview

This article explains how HTTP/3 and its QUIC transport address latency, concurrency, and content-delivery challenges in web applications. It discusses traffic engineering, network utilization, protocol design, and Zalando's experience adopting HTTP/3.

### Source excerpt

HTTP/3 addresses key challenges such as latency reduction, concurrent access, and low-latency content delivery.

## Advancing Our Amazing Bet on Asymmetric Cryptography

DevFeed: [Advancing Our Amazing Bet on Asymmetric Cryptography](<https://devfeed.tech/articles/advancing-our-amazing-bet-on-asymmetric-cryptography-4183.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2024/05/advancing-our-amazing-bet-on-asymmetric.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2024-05-23T17:19:00Z

Content type: article

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [agile](<https://devfeed.tech/tags/agile.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chrome-security](<https://devfeed.tech/tags/chrome-security.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [draft](<https://devfeed.tech/tags/draft.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [kyber](<https://devfeed.tech/tags/kyber.md>), [ml-kem](<https://devfeed.tech/tags/ml-kem.md>), [none](<https://devfeed.tech/tags/none.md>), [opt-out](<https://devfeed.tech/tags/opt-out.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [post-quantum-cryptography](<https://devfeed.tech/tags/post-quantum-cryptography.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [quantum-computer](<https://devfeed.tech/tags/quantum-computer.md>), [quic](<https://devfeed.tech/tags/quic.md>)

### AI overview

Chrome enabled the draft hybrid X25519Kyber768 key exchange by default for TLS 1.3 and QUIC on desktop in Chrome 124 to reduce store-now-decrypt-later risk. The rollout exposed existing TLS middlebox bugs, so Chrome offers a temporary enterprise opt-out; it has not launched on Android because larger Kyber messages increase latency on lower-bandwidth, higher-latency connections. Google says post-quantum authentication is also needed to prevent future impersonation, but is less urgent and harder to deploy: ML-DSA keys and signatures are much larger, and a straightforward swap could add about 14 KB to a TLS handshake. The article argues that the Web PKI first needs trust-anchor agility, allowing servers to select among multiple certificates for different clients. Cross-signing depends on CA cooperation and does not solve new-algorithm support; signature-algorithm negotiation reveals supported algorithms, not trusted anchors. Chrome proposed Trust Expressions at the IETF as one possible negotiation mechanism, while seeking community input. Google recommends prioritizing agility over immediately standardizing ML-DSA for the public Web PKI; private PKIs may have different constraints.

### Source excerpt

Google and many other organizations, such as NIST, IETF, and NSA, believe that migrating to post-quantum cryptography is important due to the large risk posed by a cryptographically-relevant quantum computer (CRQC). In August, we posted about how Chrome Security is working to protect users from the risk of future quantum computers by leveraging a new form of hybrid post-quantum cryptographic key exchange, Kyber (ML-KEM)1. We're happy to announce that we have enabled the latest Kyber draft specification by default for TLS 1.3 and QUIC on all desktop Chrome platforms as of Chrome 124.2 This rollout revealed a number of previously-existing bugs in several TLS middlebox products. To assist with the deployment of fixes, Chrome is offering a temporary enterprise policy to opt-out. Launching opportunistic quantum-resistant key exchange is part of Google's broader strategy to prioritize deploying post-quantum cryptography in systems today that are at risk if an adversary has access to a quantum computer in the future. We believe that it's important to inform standards with real-world experience, by implementing drafts and iterating based on feedback from implementers and early adopters. This iterative approach was a key part of developing QUIC and TLS 1.3. It's part of why we're launching this draft version of Kyber, and it informs our future plans for post-quantum cryptography. Chrome's post-quantum strategy prioritizes quantum-resistant key exchange in HTTPS, and increased agility in certificates from the Web PKI. While PKI agility may appear somewhat unrelated, its absence has contributed to significant delays in past cryptographic transitions and will continue to do so until we find a viable solution in this space. A more agile Web PKI is required to enable a secure and reliable transition to post-quantum cryptography on the web. To understand this, let's take a look at HTTPS and the current state of post-quantum cryptography. In the context of HTTPS, cryptography is pr

## Debugging WebRTC, IPFS & Ethereum with HTTP Toolkit

DevFeed: [Debugging WebRTC, IPFS & Ethereum with HTTP Toolkit](<https://devfeed.tech/articles/debugging-webrtc-ipfs-ethereum-with-http-toolkit-19053.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/decentralized-web-webrtc-debugging/>)

Author: HTTP Toolkit; Tim Perry

Published: 2022-10-28T13:30:00Z

Content type: article

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [WebRTC](<https://devfeed.tech/topics/webrtc.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Ethereum](<https://devfeed.tech/topics/ethereum.md>), [IPFS](<https://devfeed.tech/topics/ipfs.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [browser](<https://devfeed.tech/topics/browser.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [debugging](<https://devfeed.tech/tags/debugging.md>), [decentralized-web](<https://devfeed.tech/tags/decentralized-web.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [http](<https://devfeed.tech/tags/http.md>), [interception](<https://devfeed.tech/tags/interception.md>), [ipfs](<https://devfeed.tech/tags/ipfs.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [toolkit](<https://devfeed.tech/tags/toolkit.md>), [webrtc](<https://devfeed.tech/tags/webrtc.md>)

### AI overview

HTTP Toolkit now displays intercepted browser activity over WebRTC, IPFS, and Ethereum inline with collected HTTP traffic. Users can create rules to rewrite requests, mock responses, or inject errors, extending the tool's debugging and testing coverage to these protocols in multi-protocol web applications. The excerpt frames this as a response to applications using more communication protocols alongside HTTP, but ends before explaining how the support works internally.

### Source excerpt

HTTP is important on the web, but as other alternative protocols grow popular in networked applications, it's often important to be able to capture, debug and mock those too. I've been working on expanding HTTP Toolkit's support for this over the past year (as one part of a project funded by EU Horizon's Next Generation Internet initiative), to extend HTTP Toolkit to cover three additional rising protocols that are often used alongside simple HTTP in decentralized web applications: WebRTC, IPFS & Ethereum. This is now live! If you're using HTTP Toolkit to intercept browsers, and a web application connects to another peer over WebRTC, interacts with the Ethereum blockchain, or pulls content from the IPFS network, then you'll now see this inline amongst your collected HTTP traffic, and you can create rules to rewrite these requests, define mock responses, or inject errors. Let's talk about why this matters, what you can do with this, and how it actually works internally: Why? HTTP remains the key protocol on the web, by a wide margin, and that's not going to change any time soon. That said, there are an increasing number of new protocols being explored both alongside and on top of HTTP, covering alternate use cases and supporting different communication models, and as software evolves this will only increase. HTTP Toolkit needs to be able to support these, to ensure that you can easily understand and test all communications from the increasing number of multi-protocol applications. There's a lot of examples of HTTP-adjacent protocols where this applies: WebSockets, which grew to cover use cases needing persistent connections that weren't well supported by the request/response model, which use HTTP just for initial connection setup, and are now widely supported and used in HTTP-based apps. WebTransport, a new QUIC-based connection protocol that's aiming to supplant WebSockets with a modern approach that adds a swathe of other benefits on top. GraphQL, a general-purpose

[Next page](<https://devfeed.tech/topics/quic.md?cursor=WyIyMDIyLTEwLTI4VDEzOjMwOjAwKzAwOjAwIiwgImIwOTgzNTdhLTliOWYtNDllZS1iM2Y5LTYxZjliZmRiNjA2NiJd>)