From: Nico Williams <nico@cryptonector.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Luca Di Carlo <luca@dicarlo.email>, git@vger.kernel.org
Subject: Re: git non-intrusive clone
Date: Wed, 7 Oct 2026 15:26:28 -0500 [thread overview]
Message-ID: <asaq9MaTvtuFyrpm@ubby> (raw)
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
--
prev parent reply other threads:[~2026-10-07 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 8:40 git non-intrusive clone Luca Di Carlo
2026-10-07 18:54 ` D. Ben Knoble
2026-10-07 19:19 ` Luca Di Carlo
2026-10-07 19:50 ` D. Ben Knoble
2026-10-07 20:26 ` Nico Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=asaq9MaTvtuFyrpm@ubby \
--to=nico@cryptonector.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=luca@dicarlo.email \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.