From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: M Hickford via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, stolee@gmail.com,
Johannes.Schindelin@gmx.de, peff@peff.net,
rsbecker@nexbridge.com, M Hickford <mirth.hickford@gmail.com>
Subject: Re: [PATCH] credential: warn about git-credential-store [RFC]
Date: Sat, 1 Feb 2025 10:07:41 +0000 [thread overview]
Message-ID: <Z53ybUCIHPG78Vj2@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <pull.1856.git.1738352886190.gitgitgadget@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On 2025-01-31 at 19:48:06, M Hickford via GitGitGadget wrote:
> From: M Hickford <mirth.hickford@gmail.com>
>
> git-credential-store saves secrets unencrypted on disk.
>
> Warn the user before they type their password, suggesting alternative
> credential helpers.
>
> An alternative could be to warn in "credential-store store". A
> disadvantage is that the user wouldn't see the warning until after they
> typed their password, which is less helpful. The warning would appear
> again every time the user authenticated, which feels too frequently.
I don't think this is a good idea. While it's typically recommended to
use a different credential helper, it can be difficult to do so in an
environment where you don't have a desktop, since all of the major
helpers use the system keychain, where a desktop is required.
If you have such an environment (such as a remote system) and can't use
SSH (because your corporate environment only allows HTTPS), then you
really don't have many, if any, alternatives[0]. All warning in this
case is going to do is just annoy the user, especially if they have many
such systems.
If we are going to do this, I'd recommend using the advice system, so
that users can just disable the warning.
[0] Okay, I lied. I have a tool called Lawn (local spawn) which allows
you to run a command on your laptop or desktop from the remote machine,
such as a credential helper, but it's not in widespread use and I don't
think it's polished enough to recommend here.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2025-02-01 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:48 [PATCH] credential: warn about git-credential-store [RFC] M Hickford via GitGitGadget
2025-01-31 20:05 ` Junio C Hamano
2025-02-01 2:54 ` Jeff King
2025-02-02 23:41 ` Junio C Hamano
2025-02-01 10:07 ` brian m. carlson [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=Z53ybUCIHPG78Vj2@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mirth.hickford@gmail.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
--cc=stolee@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).