linux-kernel - Re: [GIT PULL] tracing: Updates for 4.15

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+55aFxRi6DModKgaCAzDFKPu1xBEA6zu=C-DoMWPvuEyEdfcw@mail.gmail.com>
Date:   Fri, 17 Nov 2017 15:02:46 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] tracing: Updates for 4.15

On Fri, Nov 17, 2017 at 9:20 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Tracing updates for 4.15:

.. and a new subkey for signing.

So I'll ask people who update your keys regularly (you know who you
are) to mention it when you use a new key, so that I don't go "Whaa -
why can't I recognize the signing key?"

Yes, yes, I'll just fetch it and check signatures anyway, but it gets
rid of that couple of seconds of worry about what's going on.

I guess I should remember who tends to do the yearly key updates, but
they are just infrequent enough that I never do..

            Linus