From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] asm-generic: kill <asm/segment.h> and improve nommu generic uaccess helpers
Date: Thu, 16 May 2019 14:53:43 -0700 [thread overview]
Message-ID: <1558043623.29359.44.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wiH=vGjsW9MdWFGsgto2W+71sA4XJ7CSubpXkbpC_bGKA@mail.gmail.com>
On Thu, 2019-05-16 at 13:59 -0700, Linus Torvalds wrote:
> On Thu, May 16, 2019 at 1:34 PM Arnd Bergmann <arnd@arndb.de> 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
next prev parent reply other threads:[~2019-05-16 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 12:09 Arnd Bergmann
2019-05-16 18:41 ` Linus Torvalds
2019-05-16 20:33 ` Arnd Bergmann
2019-05-16 20:59 ` Linus Torvalds
2019-05-16 21:53 ` James Bottomley [this message]
2019-05-16 22:48 ` Arnd Bergmann
2019-05-16 22:50 ` Linus Torvalds
2019-05-17 8:54 ` Geert Uytterhoeven
2019-05-16 18:45 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1558043623.29359.44.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®