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

criteria for linking to binaries from git-scm.com?

From
Jeff King <peff@peff.net>
Date
Apr 12, 2023, 08:00 UTC
Message-ID
<20230412080019.GA2172825@coredump.intra.peff.net>

There's an interesting question raised in an issue in the git-scm.com repo that I think would benefit from input from community folks here.

The link is:
  https://github.com/git/git-scm.com/issues/1774#issuecomment-1504829495
but the tl;dr is:
  From a supply chain perspective, what are our criteria for linking to
  a third party's pre-built binaries from git-scm.com?

Obviously we don't want to point people at malicious or trojaned binaries. But we probably also bear some responsibility for making sure the third party has reasonable security practices themselves.

I don't have a strong opinion myself, and this is probably a giant can of worms. But it seemed like the kind of thing that should be getting attention from the greater community, and not just languishing in that repo (both to set a policy for new requests, but also maybe to evaluate existing binaries we point to).

-Peff
Next: brian m. carlson
Message 1 of 3 in “criteria for linking to binaries from git-scm.com?”
  1. Jeff KingApr 12, 2023
  2. brian m. carlsonApr 13, 2023
  3. Derrick StoleeApr 13, 2023

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.