From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Brijesh Patel <bridgepatel@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: BUG: Value for GIT_SSL_NO_VERIFY has no effect
Date: Thu, 15 Sep 2022 13:04:47 +0000 [thread overview]
Message-ID: <YyMi76Cy7KnfZFU4@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CACs=J2MLnawNF5mp19sCJAZADPenHjWVZvKW5rM1fwELHjqqyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On 2022-09-15 at 01:46:50, Brijesh Patel wrote:
> Hi,
Hey,
> It appears that any value assigned to GIT_SSL_NO_VERIFY (true or
> false) has no effect on the GIT operations. For testing purposes, we
> have created a host entry for github.com and mapped it to foo.com.
This is definitely true. There are several Git environment variables
that act this way, including GIT_CURL_VERBOSE, that check whether the
environment is present or absent, not whether it's set to a particular
value.
I believe this behaviour is by design (although other folks are free to
correct me if they think I'e wrong).
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-09-15 13:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 1:46 BUG: Value for GIT_SSL_NO_VERIFY has no effect Brijesh Patel
2022-09-15 13:04 ` brian m. carlson [this message]
2022-09-15 15:27 ` Junio C Hamano
2022-09-15 16:06 ` [PATCH 0/5] Update docs on GIT_* environment variables Junio C Hamano
2022-09-15 16:06 ` [PATCH 1/5] environ: document GIT_SSL_NO_VERIFY Junio C Hamano
2022-09-15 16:06 ` [PATCH 2/5] environ: explain Boolean environment variables Junio C Hamano
2022-09-15 16:06 ` [PATCH 3/5] environ: GIT_FLUSH should be made a usual Boolean Junio C Hamano
2023-01-03 17:18 ` René Scharfe
2023-01-04 6:37 ` Junio C Hamano
2023-01-04 16:36 ` René Scharfe
2023-01-04 7:33 ` Jeff King
2023-01-04 16:36 ` René Scharfe
2023-01-06 9:10 ` Jeff King
2022-09-15 16:06 ` [PATCH 4/5] environ: simplify description of GIT_INDEX_FILE Junio C Hamano
2022-09-16 15:39 ` Todd Zullinger
2022-09-16 16:44 ` Junio C Hamano
2022-09-15 16:06 ` [PATCH 5/5] environ: GIT_INDEX_VERSION affects not just a new repository Junio C Hamano
2022-09-15 16:15 ` BUG: Value for GIT_SSL_NO_VERIFY has no effect brian m. carlson
2022-09-15 18:05 ` Junio C Hamano
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=YyMi76Cy7KnfZFU4@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=bridgepatel@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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