Skip to main content


pre-notification dilemmas:
daniel.haxx.se/blog/2023/03/29… - I will not tell the distros mailing list about pending #curl security vulnerabilities anymore. As requested.
#curl
in reply to daniel:// stenberg://

oh thats not great, I hope the people in charge of that mailing list reevaluate that decision
in reply to daniel:// stenberg://

What does an embargo mean? Is there any reason for the distros to not grant that?
in reply to Moanos

@moanos it just means they don't tell anyone about the issue until the planned announcement date. And no, there is no (good) reason why they cannot just grant us this - if you ask me anyway.
in reply to daniel:// stenberg://

I think that "they" in that sentence shouldn't be there

> this is an exception and they their policy says this is not acceptable for embargos.

in reply to daniel:// stenberg://

That's too bad. You have been a very regular poster there with high quality reports. I've been on the list for a while, and while I appreciate all the work solar designer does for the community there (and why he doesn't want to extend embargoes) it's clear that the way it is run doesn't work for a lot of projects. Maybe it's time for an alternative.
in reply to Johannes

@swars clearly something is wrong when neither curl, Firefox or the Linux kernel (can) post about their vulnerabilities there... But I'm not the one to tell what the alternative should be.
in reply to daniel:// stenberg://

I agree. An alternative could be a list like distros, but with no (or very lax) ground rules, where the reporters specify the rules for the embargoes. Don't know if this would work out, as this also has quite some potential for problems, but it might be worth a try.