Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by vlovich123 on Thursday April 23, 2026 @10:47PM
(#47884887)
Better for the cool down to be managed guaranteed centrally by the package forge rather than ad-hoc by each individual client.
[ Parent
| on HN ]
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by ornornor on Thursday April 23, 2026 @11:32PM
(#47885170)
That’s tricky, sometimes you really need the new version to be available right away.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by vlovich123 on Friday April 24, 2026 @02:08AM
(#47886218)
There’s ways to handle that. But that’s the exception, not the rule.
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by friendzis on Friday April 24, 2026 @03:24AM
(#47886792)
foobarizer>=1.2.3 vs foobarizer==1.2.5
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by piaste on Friday April 24, 2026 @07:16AM
(#47888610)
The cooldown is a defence against malicious actors compromising the release infrastructure.
Having the forge control it half-defeats the point; the attackers who gained permission to push a malicious release, might well have also gained permission to mark it as "urgent security hotfix, install immediately 0 cooldown".
Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha...
by vlovich123 on Friday April 24, 2026 @09:57AM
(#47890395)
I have not heard anyone seriously discuss that cooldown prevents compromise of the forge itself. It’s a concern but not the pressing concern today.
And no, however compromised packages to the forge happens, that is not the same thing as marking “urgent security hotfix” which would require manual approval from the forge maintainers, not an automated process. The only automated process would be a blackout period where automated scanners try to find issues and a cool off period where the release gets progressively to 100% of all projects that depend on it over the course of a few days or a week.