| Podcast | https://opensourcesecurity.io/ |
| Web | https://bress.net |
| Cookies? | Yes please |
| TTY | 1 |
| Signal | joshbressers.01 |
| Podcast | https://opensourcesecurity.io/ |
| Web | https://bress.net |
| Cookies? | Yes please |
| TTY | 1 |
| Signal | joshbressers.01 |
Companies will put up all kinds obstacles to responsible disclosure for researchers to get around to make their own lives easier. But they often forget that in the end it is researcher who calls the shots. It is the researchers vuln and they can do whatever they want with it.
#vulnerability #disclosure #responsibledisclosure #windows #microsoft
I had a chat with @andrewnez about why creating a new package repository is so hard. There are a ton of little details like support from SBOM and vulnerability scanners nobody even thinks about usually. There are so many little details
Andrew does a great job explaining all this and more
https://opensourcesecurity.io/2026/2026-04-ecosystems-andrew/

Josh welcomes back Andrew Nesbitt to discuss some recent blog posts he wrote about the challenges of new ecosystems as well as challenges of no ecosystems like C. There aren’t very many people who look at multiple ecosystems in the way Andrew does. He has thoughts on why it’s so hard to create a new ecosystem as well as some of the reasons we don’t see a C language ecosystem. Andrew has a ton of interesting ideas and insight for us about both existing, new, and nonexistent ecosystems.
The Cathedral and the Catacombs - Stretching a metaphor deep into the floor.
https://nesbitt.io/2026/04/06/the-cathedral-and-the-catacombs.html
If you want to see some quality AI security reports, that often identify a bug we don't think have security properties, remember that we disclose every report once closed and this is now quite a few every week:
Axios supply chain attack is interesting, partly because I'm not seeing NEARLY the traffic I'd expect to the C2 domain.
I expect some absolute chad caught it early and negotiated a very effective sinkhole.
I clearly need to start a wall of “trusted publishing would have prevented this” incidents
Edit: but not axios, maybe! Looks like that one may be full maintainer account compromise.