Wes Payne

Things Wes Says on Podcasts

Co-host of LINUX Unplugged, the Jupiter Broadcasting show on Linux, open source, self-hosting and home lab tooling, with topics ranging from NixOS and Home Assistant to Nebula mesh networking. Has hosted hundreds of LINUX Unplugged episodes and also co-hosted Coder Radio. Appears as a guest on Self-Hosted and the Ask Noah Show.

Where to Find Them

Wes Payne hosts LINUX Unplugged and hosts Coder Radio . They have also been a guest on Self-Hosted (4 times) and Ask Noah Show .

Recently: “690: The S in PHP is for Security” on LINUX Unplugged (October 2026); “689: First Kontact” on LINUX Unplugged (October 2026); “688: Eyes on Deck” on LINUX Unplugged (October 2026); “687: Linux by Proxy” on LINUX Unplugged (October 2026); “686: Stop Desktop Slop” on LINUX Unplugged (September 2026); “685: Pool Party” on LINUX Unplugged (September 2026).

What They Said

“It's really going to show us the long tail of C code that is out there that we rely on. That these were always there. And a lot of them are not like some crazy bugs that humans could never find. They're bugs that humans could find. We've just never been able to look.” — Wes Payne, LINUX Unplugged

The hosts ran through a week of vulnerabilities in PHP, the Brotli compression library, Nginx and the Linux kernel's built-in SMB server. Payne's point is that AI-assisted scanning is surfacing old bugs that were always findable but that nobody had the time to look for.

LINUX Unplugged · 2026-10-25 Permalink → Listen →
LINUX Unplugged Around 04:40 into the episode
Wes Payne

…tricky to find out. I think the default fast API stack in particular wasn't vulnerable. So it depends a lot on the specifics versus Node, they just ship it. And so you had to update Node because it was baked in. But we also saw some Nginx issues. And we saw a bunch of issues in your favorite KSMPD.

Chris Fisher

Oh, that's right. That was. Yes. Yes, of course, the kernel's built-in Samba server. Who would have thought?

Wes Payne

So, in this sort of rising tide of vulnerabilities, it's not that we will only see these issues, right? Because you can have just errors in every type of program, but it's really going to show us the long tail of C code that is out there that we rely on. That these were always there. And a lot of them are not like some crazy bugs that humans could never find. They're bugs that humans could find. We've just never been able to look. If you stack

Chris Fisher

a bunch of certain edge cases together, you could find them.

Wes Payne

And in this case, this code was flagged two years ago.

Chris Fisher

Oh, that is an interesting bit of this, yes.

Speaker names from our own diarization · position estimated from where the line sits in the episode

Collections They Appear In