killerbees commented on issue #326:
URL: 
https://github.com/apache/tooling-trusted-releases/issues/326#issuecomment-3712125400

   IMO two risks 1/ Any action by one person that could be exploited to
   introduce a malicious payload prior to distribution, by an actor using
   compromised credentials, or a trusted person stepping outside of the
   implied scope of their role, ought to require a second approval.
   Examples of the latter would include well intentioned last-minute changes
   that lack oversight.
   What we want to protect ourselves against is supply chain attacks that
   occur within the foundation and are promulgated beyond the foundation
   without being caught by automated checks.
   2/ Any irreversible loss of intellectual property.
   
   Thats all i got here.
   
   On Mon, 5 Jan 2026, 18:10 Dave Fisher, ***@***.***> wrote:
   
   > *dave2wave* left a comment (apache/tooling-trusted-releases#326)
   > 
<https://github.com/apache/tooling-trusted-releases/issues/326#issuecomment-3711560675>
   >
   > Guard these transitions.
   >
   >    - Deletion of Projects. Only allowed if there are no Releases and no
   >    Archived Releases and therefore not guarded.
   >    - Archival of Projects (and Releases) is guarded.
   >    - Archival of a Release
   >    - Deployment of a Release
   >
   > Deployment of a Release with Archival of a prior release should be
   > approved with a single request.
   >
   > The guarded action should trigger an email to the PMC's private email with
   > a link to approval.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/tooling-trusted-releases/issues/326#issuecomment-3711560675>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/ABDWS5N2LM2LX5SP5ZYQNZL4FKSKJAVCNFSM6AAAAACMIIGQEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJRGU3DANRXGU>
   > .
   > You are receiving this because you were mentioned.Message ID:
   > ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to