From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 690341F9FC for ; Fri, 26 Mar 2021 08:44:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229753AbhCZInv (ORCPT ); Fri, 26 Mar 2021 04:43:51 -0400 Received: from cloud.peff.net ([104.130.231.41]:49654 "EHLO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229892AbhCZInl (ORCPT ); Fri, 26 Mar 2021 04:43:41 -0400 Received: (qmail 29816 invoked by uid 109); 26 Mar 2021 08:43:40 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with ESMTP; Fri, 26 Mar 2021 08:43:40 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 2284 invoked by uid 111); 26 Mar 2021 08:43:42 -0000 Received: from coredump.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.94) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPS; Fri, 26 Mar 2021 04:43:42 -0400 Authentication-Results: peff.net; auth=none Date: Fri, 26 Mar 2021 04:43:39 -0400 From: Jeff King To: shadewither Cc: git@vger.kernel.org Subject: Re: How to disable git verification of ssl proxy? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Mon, Mar 22, 2021 at 11:06:31AM +0800, shadewither wrote: > git version 2.25.1 / Ubuntu 20.04 > http.sslverify=false does not work. git insists on verifying ssl proxy > and complains. > curl has an option of --proxy-insecure to disable proxy verification, > what is the equivalent for git? I don't think there is one. Peeking at the curl source code, --proxy-insecure is setting CURLOPT_PROXY_SSL_VERIFYPEER and CURLOPT_PROXY_SSL_VERIFYHOST both to 0. So I think we'd need to plumb through an http.proxysslverify option that is equivalent to http.sslverify, but using the PROXY variants with curl_easy_setopt(). -Peff