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

Re: Remembering which http remotes require authentication

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 12, 2023, 22:12 UTC
Message-ID
<xmqqh6rc72k8.fsf@gitster.g>
In-Reply-To
<CAGJzqsnkH_dtv-CGsSFJ8K0kXKBf1+QQqy=MEw-Vq9XaEqr=AQ@mail.gmail.com>
M Hickford <mirth.hickford@gmail.com> writes:
> Could Git remember which remotes require authentication for which
> operations?
Interesting idea.

Credential helpers may know which URL needed authentication before, but that is not per operation. I wonder if it is sufficient as the zeroth approximation to always try authenticated access if helpers have any auth material to the URL regardless of the operation?

There needs a way to force unautheticated access if we were to do anything of that sort, of course.

Previous: brian m. carlsonNext: M Hickford
Message 3 of 5 in “Remembering which http remotes require authentication”
  1. M HickfordJun 12, 2023
  2. brian m. carlsonJun 12, 2023
  3. Junio C HamanoJun 12, 2023
  4. M HickfordJun 21, 2023
  5. brian m. carlsonJun 21, 2023

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.