linux-kernel - Re: [GIT PULL] s390 patches for 4.19 #3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180914073756.2c208e55@mschwideX1>
Date:   Fri, 14 Sep 2018 07:37:56 +0200
From:   Martin Schwidefsky <schwidefsky@...ibm.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-s390 <linux-s390@...r.kernel.org>,
        Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [GIT PULL] s390 patches for 4.19 #3

On Thu, 13 Sep 2018 16:26:38 -1000
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, Sep 13, 2018 at 2:02 AM Martin Schwidefsky
> <schwidefsky@...ibm.com> wrote:
> >
> > this is the first try to do a pull request for s390 with a signed tag.
> > I keep my fingers crossed that the setup works as intended.
> >
> > I have used the 8A8FDAE0 signing sub-key of my 26AE5DD2 master key:  
> 
> The signed tag looks ok, but you haven't actually pushed out your new
> signing sub-key to the keyservers, so I can't actually verify it.
> 
> So a "gpg --send-key" would be a good idea.

I did push it to keys.gnupg.net, but the sub-key is brand new and 
probably takes some time to sync on the key server network.

The key is there on pgp.mit.edu this morning, it that to one you
are using or do you prefer a different one?

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.