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

Re: Checks added for CVE-2018-11235 too restrictive?

From
Mike Hommey <mh@glandium.org>
Date
Jul 4, 2018, 08:18 UTC
Message-ID
<20180704081857.kgoiniydk44ooq6v@glandium.org>
In-Reply-To
<20180703223030.xds2bfgeuaa35isj@glandium.org>
On Wed, Jul 04, 2018 at 07:30:30AM +0900, Mike Hommey wrote:
Show 5 quoted lines
> That being said, I'm not even sure this particular use case is worth a
> new feature. I'm not storing random stuff as gitlinks, I'm storing
> sha1s. Well, maybe a mode that makes the distinction between "git oid"
> and "external oid" might make things clearer for git itself, especially
> for fsck.

Actually, I'm also abusing the lower bits of the gitlink mode, to differentiate between regular files, executable files, and symlinks.

Mike
Previous: Mike Hommey
Message 6 of 6 in “Checks added for CVE-2018-11235 too restrictive?”
  1. Mike HommeyJul 3, 2018
  2. Jeff KingJul 3, 2018
  3. Junio C HamanoJul 3, 2018
  4. Jeff KingJul 3, 2018
  5. Mike HommeyJul 3, 2018
  6. Mike HommeyJul 4, 2018

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.