git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Shared repositories no longer securable against privilege escalation

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2017, 18:24 UTC
Message-ID
<xmqqinn77odv.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<195b30d7-9ea2-7a9b-79ca-41b7bb890a30@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 11 quoted lines
> The locking was added intentionally, to ensure that the reflog for
> `HEAD` is written safely. But the code didn't do that prior to the
> commit that you referenced, so (as a special case) ignoring failures to
> lock `HEAD` due to insufficient permission is probably a reasonable
> compromise.
>
> I think the special case could be restricted even further to when `HEAD`
> has the `REF_LOG_ONLY` flag in the reference transaction. I don't think
> that `HEAD` would ever show up in a transaction solely to verify its old
> value in a typical server scenario, but if so, that situation could be
> special cased too.
I find both of these acceptably good changes.
Previous: Jakub NarębskiNext: Ævar Arnfjörð Bjarmason
Message 8 of 9 in “Shared repositories no longer securable against privilege escalation”
  1. Joe RayhawkMar 17, 2017
  2. Michael HaggertyMar 17, 2017
  3. Junio C HamanoMar 17, 2017
  4. Joe RayhawkMar 17, 2017
  5. Junio C HamanoMar 17, 2017
  6. Joe RayhawkMar 17, 2017
  7. Jakub NarębskiMar 18, 2017
  8. Junio C HamanoMar 17, 2017
  9. Ævar Arnfjörð BjarmasonMar 18, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.