Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.
Carlos O'Donell <[email protected]> Thu, 25 May 2023 07:12:16 -0400
| Newsgroups | org.linuxfoundation.lists.cti-tac |
|---|---|
| Organization | Red Hat |
| Message-ID | <[email protected]> |
On 5/24/23 17:12, Siddhesh Poyarekar wrote: > On 2023-05-24 15:06, Konstantin Ryabitsev wrote: >> On Wed, May 24, 2023 at 02:13:53PM -0400, Siddhesh Poyarekar wrote: >>> It looks like the question of who to ultimately trust, either the gatekeeper >>> committer (or two) who is the only person to have write access to the >>> repository, or the admin who manages the box. >> >> The maintainer's action are in the public, while the admin's actions are >> hidden. >> >>> The gatekeeper committer could also fabricate commits and push to the >>> central repository in the same way. >> >> 1. Not with nearly as much impunity, especially if non-fast-forward pushes are >> disallowed. > > If an admin makes a change that needs a fast-forward, anybody trying > to sync their repos would see the forced update. I'll admit though > that it's arguable how many would actually notice the message. Right. Some of us would, and review the situation. Let me be clear though, Google *accidentally* force pushed on glibc master branch on 2023-01-10 and the hooks didn't stop them, and it is a known bug in our hooks. Joseph noticed and called it out... I didn't notice. Nobody else noticed because it was the most recent thing in HEAD and nobody had pulled yet. -- Cheers, Carlos.