linux-kernel - Re: [GIT PULL] apparmor fix for 4.15-rc7

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: <CA+55aFzBsMd2QhWiADn9AD7P9+MWfBoUfvaX+Me5eV5-V0XnMw@mail.gmail.com>
Date:   Sun, 7 Jan 2018 11:40:49 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     John Johansen <john.johansen@...onical.com>
Cc:     LKLM <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] apparmor fix for 4.15-rc7

On Sun, Jan 7, 2018 at 5:53 AM, John Johansen
<john.johansen@...onical.com> wrote:
>
> can you please pull the following regression fix for apparmor.

Pulled.

I do note that you still don't seem to have any signatures on your key.

You've used it for a couple of months, any chance to get somebody to sign it?

Even without signatures, it's a fine key and validates that it's the
same person (or controlling entity) that keeps doing this, but it
would be even better if there was an actual chain of trust in addition
to the basic key.

               Linus