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-ASN: AS31976 209.132.180.0/23 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, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 11A801F48C for ; Wed, 12 Feb 2020 08:56:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728570AbgBLI45 (ORCPT ); Wed, 12 Feb 2020 03:56:57 -0500 Received: from vuizook.err.no ([178.255.151.162]:56512 "EHLO vuizook.err.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728546AbgBLI44 (ORCPT ); Wed, 12 Feb 2020 03:56:56 -0500 Received: from p576124-ipngn200707tokaisakaetozai.aichi.ocn.ne.jp ([122.31.139.124] helo=glandium.org) by vuizook.err.no with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j1npF-0001tY-IG for git@vger.kernel.org; Wed, 12 Feb 2020 08:56:54 +0000 Received: from glandium by goemon.lan with local (Exim 4.92) (envelope-from ) id 1j1np8-000Un1-Kq for git@vger.kernel.org; Wed, 12 Feb 2020 17:56:46 +0900 Date: Wed, 12 Feb 2020 17:56:46 +0900 From: Mike Hommey To: git@vger.kernel.org Subject: SHA1dc on mac Message-ID: <20200212085646.hgq3nv2lf4brbb3j@glandium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG-Fingerprint: 182E 161D 1130 B9FC CD7D B167 E42A A04F A6AA 8C72 User-Agent: NeoMutt/20180716 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi, If I'm not mistaken in my reading of the various files involved, it looks like for some reason, building git on mac leads to using Apple Common Crypto for SHA1, rather than SHA1dc, which seems unfortunate. Is that really expected? More generally, at this point, should anything other than SHA1dc be supported as a build option at all? Mike