No, I don't think all people in Spain work the same number of hours. Also, I think "other European countries" are not a homogenous group, average number of hours worked differs per country.
Well people in Spain have a lot less working hours than in other European countries such as Greece, Poland, and Malta. Whether work hours means doing actual work or just loafing around is harder to measure.
From your own link, of all the EU nation states Spain is pretty much middle-of-the-pack for per-worker hours.
Another counterpoint: higher work hour countries have higher rates of death per kilometer of active track [0]
Greece (highest in the EU for work hours) = 22.3 rail deaths per 1k kilometer of track followed by Portugal (another high work hour ranking) with 6.2, Portugal (about 200 more hours than Spain annual) at 6.2, and Hungary (at about 100 more hours) at 5.8.
The only two countries with less deaths per 1K KM of track and more work hours are Ireland and Estonia. All the rest (Denmark, Sweden, Austria, Finland, Slovenia, Luxembourg) have less annual work hours than Spain.
The thing is, his reasoning isn't even wrong (assuming what he said about the spread of PoCs and the ease of finding the vuln was true), but it clearly prioritized Chainguard customers over the broader ecosystem.
It was a selfish, PR exercise. He could have done it quietly.
He could have just made sure his customers got an emergency patch quietly. (those who are willing and capable to patch)
It is not common that anyone in the public could use his source except for his customers.
It is difficult to just build from his source and drop it to any operating system and setup and expect it to work (let alone compliance and other requirements).
Instead, he expected the public to thank him like he was actually doing an act of good.
Loss for words, to be honest.
> He could have just made sure his customers got an emergency patch quietly.
I prefer them going public over breaking the embargo as silently breaking embargos and publishing details about vulnerabilities to an uncontrollably large group of unvetted people is worse.
The important thing here is that we know Chainguard's word cannot be trusted.
Chainguard will lie and cheat to put themselves first. Not their customers, but themselves. These are just plain facts.
You can't agree to an embargo and then just ignore it when you feel like it. What other things are you willing to go back on your word for, especially when you know for a fact you are putting people in danger.
> but it clearly prioritized Chainguard customers over the broader ecosystem.
I hope the broader ecosystem responds by putting their customers over Chainguard. The Chainguard customers can then get security updates after the embargo was lifted and Chainguard noticed.
The bragging by the discoverer made everyone start looking. Then when the PHP foundation made the announcement on the website there was a mad scramble. Up to 18 hours before release there were already demos. Look I get that it's a rock and a hard place but frankly at that point you should release the patch. I know there was a lot of fear over picking the wrong patch but having nothing is still bad.
and like I said in my other comment here, they could've released an OOM-only fix that would've not revealed the actual full exploit but would've protected everyone, but they decided that the only way would be to fix the whole thing and release that... it's very stupid, but seems like it's expected from them, considering it took them 2 months to get to a fix
> We used Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol throughout this research. Notably, Gemini 4 Argon made an invaluable contribution to finding the vulnerability, exploit development, attack detection, and validation of the patch.
Apparently one of the distributors that had access to the patch broke the plan and went live with it earlier. So they had to rush patches and disclosures.
These articles were supposed to come out in about a week
reply