5 ms·
Better for the cool down to be managed guaranteed centrally by the package forge rather than ad-hoc by each individual client.
by vlovich123 6mo ago
Better for the cool down to be managed guaranteed centrally by the package forge rather than ad-hoc by each individual client.
- ornornor 6mo agoThat’s tricky, sometimes you really need the new version to be available right away.
- vlovich123 6mo agoThere’s ways to handle that. But that’s the exception, not the rule.
- friendzis 6mo agofoobarizer>=1.2.3 vs foobarizer==1.2.5
- piaste 6mo agoThe 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".
- vlovich123 6mo agoI 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.
- piaste 6mo agoBy "release infrastructure" I didn't mean gain admin access to github.com, I meant gaining the credentials to push out a release of that particular package.