From: Junio C Hamano <gitster@pobox.com>
To: "M Hickford via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Taylor Blau <me@ttaylorr.com>, Glen Choo <chooglen@google.com>,
M Hickford <mirth.hickford@gmail.com>
Subject: Re: [PATCH v2] credential/libsecret: erase matching creds only
Date: Wed, 26 Jul 2023 10:15:01 -0700 [thread overview]
Message-ID: <xmqqzg3id27e.fsf@gitster.g> (raw)
In-Reply-To: <pull.1527.v2.git.git.1690387585634.gitgitgadget@gmail.com> (M. Hickford via GitGitGadget's message of "Wed, 26 Jul 2023 16:06:25 +0000")
"M Hickford via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: M Hickford <mirth.hickford@gmail.com>
>
> The credential erase request typically includes protocol, host, username
> and password.
>
> credential-libsecret erases a stored credential if it matches protocol,
> host and username, regardless of password.
>
> This is confusing in the case the stored password differs from that
> in the request. This case can occur when multiple credential helpers are
> configured.
>
> Only erase credential if stored password matches request (or request
> omits password).
This is much better.
> This fixes test "helper ... does not erase a password distinct from
> input" introduced in aeb21ce22e (credential: avoid erasing distinct
> password, 2023-06-13)
This was still confusing for a patch that does not touch anything in
t/, but after re-reading aeb21ce22e and the above a few times, I
think I get it. Adding the following
, when t0303 is run with GIT_TEST_CREDENTIAL_HELPER set to
"libsecret".
at the end may help, but perhaps it is too obvious for folks who are
ready to actually review this change---presumably they are familiar
with how t0303 is to be used and read that without being told from
the context?
Thanks.
next prev parent reply other threads:[~2023-07-26 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 7:21 [PATCH] credential/libsecret: erase matching creds only M Hickford via GitGitGadget
2023-07-26 16:06 ` [PATCH v2] " M Hickford via GitGitGadget
2023-07-26 17:15 ` Junio C Hamano [this message]
2023-07-26 19:44 ` M Hickford
2023-07-26 19:46 ` [PATCH v3] " M Hickford via GitGitGadget
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=xmqqzg3id27e.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=mirth.hickford@gmail.com \
--cc=peff@peff.net \
/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).