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

Re: [PATCH] http.c: fix parsing of http.sslCertPasswordProtected variable

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 12, 2013, 19:52 UTC
Message-ID
<7vtxjzk13q.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130712190531.GD8482@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
> FWIW the GIT_SSL_CERT_PASSWORD_PROTECTED envvar has a similar "can
> only enable" behavior, but since it's documented, that's not as big
> of a problem.  Do you remember why it was written that way?
Not me ;-).

If I have to guess, it is probably that these two are thought to be equally trivial way to defeat existing environment settings:

	(unset GIT_SSL_CERT_PASSWORD_PROTECTED ; git cmd)
        GIT_SSL_CERT_PASSWORD_PROTECTED=no git cmd
> When that setting was first added[1], there was some mention of
> autodetection if libcurl could learn to do that.  Did it happen?

I do not think so, but let's see if our resident cURL guru has something to say about it.

Previous: Jonathan NiederNext: Mark Lodato
Message 3 of 8 in “http.c: fix parsing of http.sslCertPasswordProtected variable”
  1. http.c: fix parsing of http.sslCertPasswordProtected variableJunio C Hamano, Jul 12, 2013
  2. Jonathan NiederJul 12, 2013
  3. Junio C HamanoJul 12, 2013
  4. Mark LodatoJul 14, 2013
  5. Junio C HamanoJul 15, 2013
  6. Kyle J. McKayJul 15, 2013
  7. Junio C HamanoJul 15, 2013
  8. Kyle J. McKayJul 13, 2013

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.