From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Patrick Steinhardt <ps@pks.im>, Taylor Blau <me@ttaylorr.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Karthik Nayak <karthik.188@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
"brian m . carlson" <sandals@crustytoothpaste.net>,
"Randall S . Becker" <rsbecker@nexbridge.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v5 3/3] promisor-remote: compare remote names case sensitively
Date: Fri, 14 Mar 2025 10:28:37 -0700 [thread overview]
Message-ID: <xmqqo6y3h67u.fsf@gitster.g> (raw)
In-Reply-To: <20250314141203.2548803-4-christian.couder@gmail.com> (Christian Couder's message of "Fri, 14 Mar 2025 15:12:03 +0100")
Christian Couder <christian.couder@gmail.com> writes:
> Because the "[remote "nick"] fetch = ..." configuration variables
> have the nickname in the second part, the nicknames are case
> sensitive, unlike the first and the third component (i.e.
> "remote.origin.fetch" and "Remote.origin.FETCH" are the same thing,
> but "remote.Origin.fetch" and "remote.origin.fetch" are different).
I double-checked what the control flow that passes through
remote.c:handle_config() does, and the above is in line with what
remote_get() does.
remote.c:read_config() populates the nickname-to-remote hashmap by
using handle_config() callback, which calls make_remote() with the
second level name (e.g. "Origin" and "origin" in the last example of
the above), which is passed to memhash() not memihash() when looking
up or registering the remote.
If we used case insensitive comparison in the new code, a malicious
large-object promisor remote could have told us to use "Origin" as
an extra promisor and in response the new code may noticed that we
have "origin" and tried to equate it with what the other side told
us. But when the existing code actually interacts with the promisor
remote, it wouldn't have found any configured remote under the name
"Origin", and something funny would start from there. By using the
right remote consistently throughout the system, we would not get
confused that way, which is good.
> Let's follow the way Git works in general and compare the remote
> names case sensitively when processing advertised remotes.
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> Documentation/config/promisor.adoc | 4 ++--
> promisor-remote.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Looking good. Thanks.
> diff --git a/Documentation/config/promisor.adoc b/Documentation/config/promisor.adoc
> index 9192acfd24..2638b01f83 100644
> --- a/Documentation/config/promisor.adoc
> +++ b/Documentation/config/promisor.adoc
> @@ -26,5 +26,5 @@ promisor.acceptFromServer::
> server will be accepted. By accepting a promisor remote, the
> client agrees that the server might omit objects that are
> lazily fetchable from this promisor remote from its responses
> - to "fetch" and "clone" requests from the client. See
> - linkgit:gitprotocol-v2[5].
> + to "fetch" and "clone" requests from the client. Name and URL
> + comparisons are case sensitive. See linkgit:gitprotocol-v2[5].
> diff --git a/promisor-remote.c b/promisor-remote.c
> index 0b7b1ec45a..5801ebfd9b 100644
> --- a/promisor-remote.c
> +++ b/promisor-remote.c
> @@ -370,13 +370,13 @@ char *promisor_remote_info(struct repository *repo)
>
> /*
> * Find first index of 'nicks' where there is 'nick'. 'nick' is
> - * compared case insensitively to the strings in 'nicks'. If not found
> + * compared case sensitively to the strings in 'nicks'. If not found
> * 'nicks->nr' is returned.
> */
> static size_t remote_nick_find(struct strvec *nicks, const char *nick)
> {
> for (size_t i = 0; i < nicks->nr; i++)
> - if (!strcasecmp(nicks->v[i], nick))
> + if (!strcmp(nicks->v[i], nick))
> return i;
> return nicks->nr;
> }
next prev parent reply other threads:[~2025-03-14 17:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:40 [PATCH] promisor-remote: fix segfault when remote URL is missing Christian Couder
2025-03-10 16:29 ` Junio C Hamano
2025-03-11 15:24 ` Christian Couder
2025-03-11 16:57 ` Junio C Hamano
2025-03-11 15:24 ` [PATCH v2] " Christian Couder
2025-03-11 16:59 ` Junio C Hamano
2025-03-12 11:48 ` Christian Couder
2025-03-11 20:48 ` Junio C Hamano
2025-03-12 11:47 ` Christian Couder
2025-03-11 23:06 ` Jeff King
2025-03-11 23:36 ` Junio C Hamano
2025-03-12 11:47 ` Christian Couder
2025-03-12 11:46 ` [PATCH v3] " Christian Couder
2025-03-12 17:02 ` Junio C Hamano
2025-03-13 10:39 ` Christian Couder
2025-03-13 16:40 ` Junio C Hamano
2025-03-14 14:09 ` Christian Couder
2025-03-14 17:28 ` Junio C Hamano
2025-03-13 10:38 ` [PATCH v4] " Christian Couder
2025-03-13 16:28 ` Junio C Hamano
2025-03-13 17:23 ` Junio C Hamano
2025-03-14 14:10 ` Christian Couder
2025-03-14 14:12 ` [PATCH v5 0/3] "promisor-remote" capability fixes Christian Couder
2025-03-14 14:12 ` [PATCH v5 1/3] promisor-remote: fix segfault when remote URL is missing Christian Couder
2025-03-14 18:59 ` Junio C Hamano
2025-03-18 11:03 ` Christian Couder
2025-03-14 14:12 ` [PATCH v5 2/3] promisor-remote: fix possible issue when no URL is advertised Christian Couder
2025-03-14 14:12 ` [PATCH v5 3/3] promisor-remote: compare remote names case sensitively Christian Couder
2025-03-14 17:28 ` Junio C Hamano [this message]
2025-03-18 11:04 ` Christian Couder
2025-03-18 11:00 ` [PATCH v6 0/4] "promisor-remote" capability fixes Christian Couder
2025-03-18 11:00 ` [PATCH v6 1/4] t5710: arrange to delete the client before cloning Christian Couder
2025-03-18 11:00 ` [PATCH v6 2/4] promisor-remote: fix segfault when remote URL is missing Christian Couder
2025-03-18 11:00 ` [PATCH v6 3/4] promisor-remote: fix possible issue when no URL is advertised Christian Couder
2025-03-18 11:00 ` [PATCH v6 4/4] promisor-remote: compare remote names case sensitively Christian Couder
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=xmqqo6y3h67u.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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).