Skip to main content
Software Engineering Daily

Inside China’s Great Firewall with Jackson Sippe

58 min episode · 2 min read
·
Jackson Sippe

Episode

58 min

Read time

2 min

Topics

Design & UX, Software Development, Science & Discovery

AI-Generated Summary

Key Takeaways

  • Pop Count Detection Threshold: The GFW's blocking algorithm counts set bits per byte and flags traffic as encrypted when the ratio falls between 3.4 and 4.6 out of 8 bits — approximately 50% density. Understanding this exact threshold lets proxy developers craft payloads that deliberately fall outside this range, restoring connectivity without requiring protocol redesign.
  • Bit-Stuffing Circumvention with 17% Overhead: Proxy developers can defeat pop count detection by padding encrypted payloads with additional ones or zeros, keyed pseudorandomly to avoid pattern detection, then appending a few bytes encoding the removal count. This technique carries roughly 17.6% bandwidth overhead — tolerable given existing proxy layering costs — and is now implemented in ShadowSocks Rust and ShadowSocks Android.
  • Emergency Header Prepending: Before the full pop count solution was ready, researchers discovered that prepending the first four bytes of a standard TLS handshake to any fully encrypted payload bypassed GFW blocking immediately. Proxy developers received this finding in January 2022 as a rapid patch, restoring service while the more robust bit-stuffing approach was developed and validated.
  • False Positive Rate Validation via University Traffic: Researchers validated their reverse-engineered ruleset by running it against University of Colorado campus traffic — a population with no reason to use circumvention tools. The resulting 0.6% false positive rate was further reduced when most flagged packets proved to be torrent protocol traffic, which the GFW likely intended to block anyway.
  • Protocol Fingerprint Exemptions Filter ~80% of Traffic First: Before applying the computationally expensive entropy check, the GFW exempts traffic matching known protocol byte signatures — TLS alone accounts for roughly 80% of all traffic. Proxy developers can exploit this by prepending recognized protocol headers, and understanding this layered exemption architecture helps engineers predict which traffic patterns will trigger or bypass inspection.

What It Covers

PhD researcher Jackson Sippe explains how China's Great Firewall deployed a passive, entropy-based detection algorithm from November 2021 to March 2023 to block fully encrypted proxy protocols used by millions of circumvention tool users, how his team reverse-engineered the pop count technique, and what countermeasures proxy developers implemented.

Key Questions Answered

  • Pop Count Detection Threshold: The GFW's blocking algorithm counts set bits per byte and flags traffic as encrypted when the ratio falls between 3.4 and 4.6 out of 8 bits — approximately 50% density. Understanding this exact threshold lets proxy developers craft payloads that deliberately fall outside this range, restoring connectivity without requiring protocol redesign.
  • Bit-Stuffing Circumvention with 17% Overhead: Proxy developers can defeat pop count detection by padding encrypted payloads with additional ones or zeros, keyed pseudorandomly to avoid pattern detection, then appending a few bytes encoding the removal count. This technique carries roughly 17.6% bandwidth overhead — tolerable given existing proxy layering costs — and is now implemented in ShadowSocks Rust and ShadowSocks Android.
  • Emergency Header Prepending: Before the full pop count solution was ready, researchers discovered that prepending the first four bytes of a standard TLS handshake to any fully encrypted payload bypassed GFW blocking immediately. Proxy developers received this finding in January 2022 as a rapid patch, restoring service while the more robust bit-stuffing approach was developed and validated.
  • False Positive Rate Validation via University Traffic: Researchers validated their reverse-engineered ruleset by running it against University of Colorado campus traffic — a population with no reason to use circumvention tools. The resulting 0.6% false positive rate was further reduced when most flagged packets proved to be torrent protocol traffic, which the GFW likely intended to block anyway.
  • Protocol Fingerprint Exemptions Filter ~80% of Traffic First: Before applying the computationally expensive entropy check, the GFW exempts traffic matching known protocol byte signatures — TLS alone accounts for roughly 80% of all traffic. Proxy developers can exploit this by prepending recognized protocol headers, and understanding this layered exemption architecture helps engineers predict which traffic patterns will trigger or bypass inspection.

Notable Moment

Researchers discovered that the GFW used its own HTTP traffic as a weapon against GitHub in 2015 — injecting JavaScript into every unencrypted request crossing the border to generate what became the largest denial-of-service attack ever recorded, simply because GitHub refused to block proxy-hosting pages.

Know someone who'd find this useful?

Episode Transcript

China's Great Firewall, or GFW, is often spoken about but is rarely understood. It is one of the most sophisticated and opaque censorship systems on the planet, and it shapes how over a billion people interact with the global Internet, influences the design of privacy and proxy tools worldwide, and continues to evolve in ways that challenge researchers, developers, and policymakers alike. Jackson Sipp is a PhD researcher at the University of Colorado Boulder whose work focuses on uncovering how national scale censorship systems operate. Jackson recently helped delete a groundbreaking study analyzing a previously undocumented GFW technique that quietly broke fully encrypted proxy protocols across China for more than a year. In this episode, Jackson joins Gregor Van to discuss how the Great Firewall works at a technical level, the twenty twenty one to twenty twenty three blocking event, the pop count based detection algorithm his team reverse engineered, the cat and mouse ecosystem of censorship circumvention, and what these findings mean for the future of the open Internet. Gregor Vand is a security focused technologist, having previously been a CTO across cybersecurity, cyber insurance, and general software engineering companies. He is based in Singapore and can be found via his profile at van.hk or on LinkedIn. Hello and welcome to Software Engineering Daily. My guest today is Jackson Sipp. Hey. Happy to be here. Yeah. So we're gonna be getting into a pretty interesting topic with Jackson today around what is called the GFW, so the great firewall, and we'll get into what even that is. But also Jackson's done a lot of research into how it operates and actually sort of how it operates through the years because it's been changing as well. So before we get into all that as we like to do, maybe just sort of, Jackson, what is your background? How did you get into this kind of research in the first place? Yeah. Sure. So, yeah, I am currently a PhD student at the University of Colorado, Boulder, and I've been here for about five years now. I'm advised by doctor Eric Wistrow, who's been doing this work for a ways longer than that. And as I first started my PhD, I got involved with an organization called the GFW report that has focused on censorship within China. And so through working with them, I've done a number of different projects sort of exploring the relationship between China and censorship. Awesome. So maybe let's just get into what is I always kinda get the acronym mixed up because I think there should be a c in there somewhere because it's sort of like the great Chinese firewall perhaps. But, yeah, maybe what is the GFW? So the GFW is the great firewall as it's known, tends to refer to the censorship mechanism in China. That acronym has sort of expanded as it's gained popularity. Sometimes people refer to Iran's GFW, so we often refer to it as China's GFW now. And it's …

Get the full transcript (10,309 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →

You just read a 3-minute summary of a 55-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • This technique carries roughly 17.6% bandwidth overhead — tolerable given existing proxy layering costs — and is now implemented in ShadowSocks Rust and ShadowSocks Android.
  • SPONSORS [Recall.ai](https://recall.ai/software)
  • SPONSORS [Retool](https://retool.com/se-daily)
  • This technique carries roughly 17.6% bandwidth overhead — tolerable given existing proxy layering costs — and is now implemented in ShadowSocks Rust and ShadowSocks Android.
  • SPONSORS [GuardSquare](https://www.guardsquare.com)

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime