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.133.124]) by sourceware.org (Postfix) with ESMTPS id 2BF0A385735B for ; Mon, 27 Jun 2022 17:23:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2BF0A385735B 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-632-LNoYW0GzOcaLFatAPs_dew-1; Mon, 27 Jun 2022 13:23:40 -0400 X-MC-Unique: LNoYW0GzOcaLFatAPs_dew-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3376880029D; Mon, 27 Jun 2022 17:23:40 +0000 (UTC) Received: from greed.delorie.com (unknown [10.22.8.54]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0F0A640CFD05; Mon, 27 Jun 2022 17:23:40 +0000 (UTC) Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.15.2/8.15.2) with ESMTP id 25RHNb7T038671; Mon, 27 Jun 2022 13:23:37 -0400 From: DJ Delorie To: Mark Wielaard Cc: siddhesh@gotplt.org, libc-alpha@sourceware.org, carlos@redhat.com Subject: Re: patchwork upgrade week In-Reply-To: Date: Mon, 27 Jun 2022 13:23:37 -0400 Message-ID: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, 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 X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2022 17:23:46 -0000 Mark Wielaard writes: > If not, how else can we authenticate a patch as "OK to let the > buildbot do a try build?" [/me is back from vacation] The method we're using to add this type of authentication is GPG-signed emails. I.e. an authorized user would reply to the patch email, in the reply give a command to their runners, and sign the command. The system would authenticate the signature and authorize the runners to act as instructed. Example: In-Reply-To:... ... Joe User wrote: > > The patch > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 %cicd buildbot expensive-hosts . . . -----BEGIN PGP SIGNATURE----- . . . -----END PGP SIGNATURE----- Each runner decides whose commands they honor, and which, and how. The curator manages the authentication, so only one keyring is needed. Note that our existing 32-bit trybot does not use this; it assumes patches may be malicious and plans accordingly. This allows it to proactively test all posted patches.