# Support SSL_CERT_DIR 2 messages from 2022-09-20 to 2022-09-21. Participants: Marcin Wisnicki, brian m. carlson. Thread: https://gitlist.dev/t/58478 ## Marcin Wisnicki, 2022-09-20 22:00 Subject: Support SSL_CERT_DIR Message-ID: URL: https://gitlist.dev/e/CAC9GOO8Y%2B5pXWPSPhxFdugT66MZj1rKkZ1Td%3DfrPTF8vo73Nhw%40mail.gmail.com ``` 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. Please CC, I'm not subscribed. ``` ## brian m. carlson, 2022-09-21 21:26 Subject: Re: Support SSL_CERT_DIR Message-ID: URL: https://gitlist.dev/e/YyuBoU1ZPaHiSeiU%40tapette.crustytoothpaste.net In-Reply-To: ``` 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 ```