Comment on Curl/libcurl HIGH CVE-2023-38545 leaked early?parentComments−justinclift2yThat kind of approach leads to the party which broke ranks this time, not being included in confidential things in future.Along the lines of "they've proven they can't be trusted", kind of thing.−junon2yI don't agree they broke ranks. The 6am date was for the curl project itself.−justinclift2yProbably depends on whether Red Hat was party to privileged info as part of a co-ordinated release for this. Personally, I have no idea.−junon2yI'd be surprised if not, but even then, it's not clear if the time was a requirement set by the cURL team at all for projects that aren't cURL.
Comments
That kind of approach leads to the party which broke ranks this time, not being included in confidential things in future.
Along the lines of "they've proven they can't be trusted", kind of thing.
I don't agree they broke ranks. The 6am date was for the curl project itself.
Probably depends on whether Red Hat was party to privileged info as part of a co-ordinated release for this. Personally, I have no idea.
I'd be surprised if not, but even then, it's not clear if the time was a requirement set by the cURL team at all for projects that aren't cURL.