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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 15 Dec 2020 06:57:02 +0200
From:   Jarkko Sakkinen <>
To:     Linus Torvalds <>
Cc:     David Howells <>,
        "Alexander A. Klimov" <>,
        "Gustavo A. R. Silva" <>,
        Alex Shi <>,
        Ben Boeckel <>,
        Denis Efremov <>,
        Gabriel Krisman Bertazi <>,
        Jann Horn <>,
        Krzysztof Kozlowski <>,
        Mickaël Salaün <>,
        Mimi Zohar <>,
        Randy Dunlap <>,
        Tianjia Zhang <>,
        Tom Rix <>, YueHaibing <>,,
        Linux Crypto Mailing List <>,
        Linux Kernel Mailing List <>,
        LSM List <>
Subject: Re: [GIT PULL] keys: Collected minor fixes and cleanups

On Mon, Dec 14, 2020 at 12:49:27PM -0800, Linus Torvalds wrote:
> The pain just isn't worth it, but more importantly, you simply need to
> get your workflow in order, and not send me completely untested
> garbage that hasn't even been compiled.

I have now more bandwidth. It was mostly eaten by SGX, especially last
few months. Starting from next week, I'll start proactively test keyring
changes (I'm this week on vacation).

I've been thinking that maybe a two-folded approach would make sense for

1. I would pick fixes to my linux-tpmdd where they would get quickly
   mirrored to linux-next. It's already taking changes for trusted
   keys, i.e. not solely for TPM changes.
2. Feature changes would go through David's tree.

>                Linus


Powered by blists - more mailing lists