From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4841C04AAF for ; Thu, 16 May 2019 21:53:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AA7A82082E for ; Thu, 16 May 2019 21:53:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="Ej9cKsPY"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="Ej9cKsPY" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728851AbfEPVxq (ORCPT ); Thu, 16 May 2019 17:53:46 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:38288 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726586AbfEPVxq (ORCPT ); Thu, 16 May 2019 17:53:46 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 89A8F8EE109; Thu, 16 May 2019 14:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1558043625; bh=jjQxK8gG30fC8ztphEl/+NchX6EWOkygL8i2PMuVq9U=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=Ej9cKsPYRiVs3hKWegxKZYbVTyWhjFJDipWtVAXw++pT/OjiGnooSR170YcM1C3Iz irU3Cw8B+qD/zqpfXRluw303d1dzUV6uSi3lTX61vTQE6bXvJQPFT2Tle/T2YDMksF mqPFgSEU19WymQeFDf8Ozh3PxPh0zTcNc03cylqg= Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mfCEGp6lPT57; Thu, 16 May 2019 14:53:45 -0700 (PDT) Received: from [153.66.254.194] (unknown [50.35.68.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id D48728EE062; Thu, 16 May 2019 14:53:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1558043625; bh=jjQxK8gG30fC8ztphEl/+NchX6EWOkygL8i2PMuVq9U=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=Ej9cKsPYRiVs3hKWegxKZYbVTyWhjFJDipWtVAXw++pT/OjiGnooSR170YcM1C3Iz irU3Cw8B+qD/zqpfXRluw303d1dzUV6uSi3lTX61vTQE6bXvJQPFT2Tle/T2YDMksF mqPFgSEU19WymQeFDf8Ozh3PxPh0zTcNc03cylqg= Message-ID: <1558043623.29359.44.camel@HansenPartnership.com> Subject: Re: [GIT PULL] asm-generic: kill and improve nommu generic uaccess helpers From: James Bottomley To: Linus Torvalds , Arnd Bergmann Cc: Christoph Hellwig , Linux Kernel Mailing List , linux-arch , linux-riscv@lists.infradead.org Date: Thu, 16 May 2019 14:53:43 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2019-05-16 at 13:59 -0700, Linus Torvalds wrote: > On Thu, May 16, 2019 at 1:34 PM Arnd Bergmann wrote: > > > > > > I have reconfigured it locally now and pushed an identical tag with > > a > > new signature. Can you see if that gives you the same warning if > > you > > try to pull that? > > No, same issue: The problem seems to be this: jejb@jarvis:~> gpg --list-keys 60AB47FFC9095227 pub rsa4096 2011-10-27 [C] 88AFCD206B1611957187F16B60AB47FFC9095227 sub rsa4096 2011-10-27 [E] Your key is a "Certification key" and you have an encryption subkey but no signing key at all. Usually you either have a signing subkey or your master key is both certification and signing ([CS] flags). Certification keys can only be used to certify other keys, they can't be used for signing, but I bet gpg is assuming that it can sign with the master key even if it doesn't possess the signing flag. You can make your master key a signing key by doing gpg --expert --edit-key 60AB47FFC9095227 Then doing gpg> change-usage and selecting "toggle sign" Or you could just add a signing subkey. In either case you'll need to save and sign the changes and then push to a keyserver for the rest of us to see it. James