git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Marcin Wisnicki <mwisnicki@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Support SSL_CERT_DIR
Date: Wed, 21 Sep 2022 21:26:57 +0000	[thread overview]
Message-ID: <YyuBoU1ZPaHiSeiU@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAC9GOO8Y+5pXWPSPhxFdugT66MZj1rKkZ1Td=frPTF8vo73Nhw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

On 2022-09-20 at 22:00:11, Marcin Wisnicki wrote:
> Is there any good reason why git ignores well established SSL_CERT_DIR
> and uses only git-specific GIT_SSL_CAPATH?
> Why not fallback to the standard variable if git one isn't set?
> IMHO current behavior is bad UX.

It looks like that variable is specific to OpenSSL.  Git may use a
variety of TLS libraries, and typically on Linux distributions, which
cannot legally distribute both Git and OpenSSL linked together, the TLS
library isn't OpenSSL at all.

Personally, I've never heard of this environment variable before, so it
probably wasn't chosen because nobody else had heard of it, either. It's
possible if someone sent a patch to check it such a change might be
accepted (or not).
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2022-09-21 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 22:00 Support SSL_CERT_DIR Marcin Wisnicki
2022-09-21 21:26 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YyuBoU1ZPaHiSeiU@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=mwisnicki@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).