From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <git-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS3215 2.6.0.0/16
X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.2
Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20])
	by dcvr.yhbt.net (Postfix) with ESMTP id 4660F1F8C4
	for <e@yhbt.net>; Wed, 16 Mar 2022 14:34:16 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233160AbiCPOf1 (ORCPT <rfc822;e@yhbt.net>);
        Wed, 16 Mar 2022 10:35:27 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58382 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S231713AbiCPOfZ (ORCPT <rfc822;git@vger.kernel.org>);
        Wed, 16 Mar 2022 10:35:25 -0400
Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66E0133E3A
        for <git@vger.kernel.org>; Wed, 16 Mar 2022 07:34:11 -0700 (PDT)
Received: from Mazikeen (cpe00fc8d49d843-cm00fc8d49d840.cpe.net.cable.rogers.com [99.229.22.139] (may be forged))
        (authenticated bits=0)
        by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 22GEYAiP029060
        (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
        for <git@vger.kernel.org>; Wed, 16 Mar 2022 10:34:10 -0400 (EDT)
        (envelope-from rsbecker@nexbridge.com)
Reply-To: <rsbecker@nexbridge.com>
From:   <rsbecker@nexbridge.com>
To:     <git@vger.kernel.org>
Subject: [RFE] Signing using SSL
Date:   Wed, 16 Mar 2022 10:34:05 -0400
Organization: Nexbridge Inc.
Message-ID: <036701d83942$e6963ca0$b3c2b5e0$@nexbridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adg5QThAIZRqvsEPRQ6E2AAZWUfL4A==
Content-Language: en-ca
Precedence: bulk
List-ID: <git.vger.kernel.org>
X-Mailing-List: git@vger.kernel.org

Following up on our IRC discussion on Monday, I have had a request to
support signing git commits and tags with SSL certificates instead of
SSH/GPG. The organization is heavily invested in SSL infrastructure, so they
want to go down that path.

The basic technique for doing this is, for example:

openssl dgst -sha256 -sign key -out content.sha256 signature.txt -passin
passphrase

There is a pre-step to compute the sha256, in this example, into a file
provided to openssl. We could use openssl to compute the hash also.

Verification is a bit different than what SSH or GPG does:

openssl dgst -sha256 -verify  <(openssl x509 -in certificate -pubkey -noout)
-signature sign.txt.sha256 signature.txt

and reports either

Verified OK
Or
Verification Failure

It does not look like completion codes are consistently involved.

This also does look structurally different than both GPG and SSH and more
work to set up. It may be possible to provide wrappers and pretend we are in
SSH, but I'm not sure that is the right path to take.

Any pointers on how this might be done in existing git infrastructure, or
should I look into making this work in code? Sorry to say that the
documentation is not that clear on this.

Thanks in advance,
Randall

--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.