Post #4448780

2026-08-08 21:21 UTC

No one in the seven-person curl security team is on or runs Windows. People sending us Windows-only flaws makes us groan and roll eyes. And sometimes hyperventilate a little. Why this is so? Because no one in the team wants to be on Windows, and no other curl contributor is active enough, Windows-knowledgeable and interested in joining the team. Let me know if you are someone like that who I've just not noticed.

Replies (4)

@paul_ipv6@infosec.exchange 2026-08-08 21:26

@bagder@mastodon.social from my memories of doing support for a different FOSS project, one issue is not just finding an interested and competent person. they have to have all the right licenses and certs so they have access to the latest micro$quish compilers and M$ support. it's so painful for so many reasons that didn't need to be except micro$quish...

Open ##4448779
@varx@infosec.exchange 2026-08-08 21:40

@bagder@mastodon.social I recently tried to cross-compile a small Rust program for Mac and discovered that in order to do so, I would have to sign some kind of developer agreement? Nope, don't feel like reading through all that. I can only imagine what it's like developing for Windows. Just compiling for Linux for now.

Open ##4449238
@flyingpenguin@infosec.exchange 2026-08-08 22:11

@bagder@mastodon.social I maintain a Windows 11 system to support Wirken.AI users stuck on it (usually lawyers). It's been a real thorn, but I could maybe offer help to the curl team as I'm already supporting it myself.

Open ##4450016
@SpaceLifeForm@infosec.exchange 2026-08-08 22:46

@bagder@mastodon.social Is not the Q+D workaround to just use WSL?

Open ##4450771