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

Re: git non-intrusive clone

From
NWNico Williams <nico@cryptonector.com>
Date
Oct 7, 2026, 20:26 UTC
Message-ID
<asaq9MaTvtuFyrpm@ubby>
In-Reply-To
<CALnO6CA5tY5Ebw5JyA8c-e00PqLcXMAijA5VF6DrPJNDCX=raA@mail.gmail.com>
On Wed, Oct 07, 2026 at 03:50:43PM -0400, D. Ben Knoble wrote:
> Still, definitely worth having the conversation, and I'm glad we
> figured it out together. I'm still somewhat interested in what we can
> do besides "try to tell folks not to blindly trust downloaded files"…
> but that's never going to stop being bad advice :)

There have been horror stories about phishing via fake interviews. There is no easy way to ascertain the trustworthiness of such code. Just don't run that code. Use a hosted VM service for this or insist that they use a code pad type web application -- that they don't use those is a red flag.

Nico
Previous: D. Ben Knoble
Message 5 of 5 in “git non-intrusive clone”
  1. Luca Di CarloOct 7, 2026
  2. D. Ben KnobleOct 7, 2026
  3. Luca Di CarloOct 7, 2026
  4. D. Ben KnobleOct 7, 2026
  5. Nico WilliamsOct 7, 2026

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.