Implement a package cooldown period setting.
A package cooldown gives maintainers time to catch and withdraw a bad release by holding each new version, including dependencies, for a set period such as 72 hours. Repository mirror: Stage upstream updates and publish only approved versions after the waiting period, so every APT and Yum/DNF client gets the same policy. Client-side: Without a mirror, each machine records when it first sees a build and filters fresh versions using APT pins plus an install hook or a DNF plugin. Emergency patch bypass: Use the vendor advisory to approve the exact fixed build and any required dependencies for one transaction, keeping signature verification active and letting the exception expire afterward.
Feature set suggestion:
a programmable cooldown length (in days).
a way to bypass that based on known good verifed patch from the vendor for a zero day vlun mitigation.
a check to prevent install of a patch or package with a known vuln.
a way to bypass that based on evaluated or acceptable risk.
0 Comments
No comments yet. Be the first to share your thoughts.
