From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id AB2B93858C62 for ; Wed, 5 Jul 2023 20:01:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AB2B93858C62 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688587296; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZPI9tJfAuDKUkH0LDWETmmStELKFPmSQT7G0QTf0RLs=; b=DxHZUq0VJG7UEc3K0MRVtSxRLLpjFz3ZkB5cD/8R3oK4l33QpbxPEtzcTFrsPAGmgEjLvv hN7sw2At9ZTg6FouIcIcBKK+q3EqEZiTtaQH3PwnDsMwevJ4wMcTrq9hQB2Wdd4iA15TpT sRwZEihVcsTWUVyvYlvFzSTNaAUYBiw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-615-mSZudF2HOc6OfyZHT-JIbg-1; Wed, 05 Jul 2023 16:01:32 -0400 X-MC-Unique: mSZudF2HOc6OfyZHT-JIbg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5F7D1101A528; Wed, 5 Jul 2023 20:01:32 +0000 (UTC) Received: from redhat.com (unknown [10.22.32.43]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1F417C478DD; Wed, 5 Jul 2023 20:01:32 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1qH8gt-0006CX-88; Wed, 05 Jul 2023 16:01:31 -0400 Date: Wed, 5 Jul 2023 16:01:31 -0400 From: "Frank Ch. Eigler" To: Overseers mailing list Cc: Mark Wielaard , "Frank Ch. Eigler" , Ludovic =?iso-8859-1?Q?Court=E8s?= Subject: Re: gitsigur for protecting git repo integrity Message-ID: <20230705200131.GI25859@redhat.com> References: <20230704083245.GB11693@gnu.wildebeest.org> <20230705182544.GF11693@gnu.wildebeest.org> MIME-Version: 1.0 In-Reply-To: <20230705182544.GF11693@gnu.wildebeest.org> User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - > My understanding is that gitsigur checks signatures against an > out-of-band list of authorized keys, which isn’t very useful because > the set of authorized committers changes over time. The list of authorized keys is stored in a selected branch of a selected git repo, whose contents may change over time (and: maintain an audit trail) (and: may itself be protected by security mechanisms such as gitsigur). - FChE