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]
Date:   Fri, 4 Nov 2022 21:06:27 +0000
From:   Eric Snowberg <eric.snowberg@...cle.com>
To:     Coiby Xu <coxu@...hat.com>
CC:     "davem@...emloft.net" <davem@...emloft.net>,
        David Howells <dhowells@...hat.com>,
        "dmitry.kasatkin@...il.com" <dmitry.kasatkin@...il.com>,
        "dwmw2@...radead.org" <dwmw2@...radead.org>,
        "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
        jarkko Sakkinen <jarkko@...nel.org>,
        "jmorris@...ei.org" <jmorris@...ei.org>,
        Konrad Wilk <konrad.wilk@...cle.com>,
        Kanth Ghatraju <kanth.ghatraju@...cle.com>,
        Elaine R Palmer <erpalmer@...ibm.com>,
        "keyrings@...r.kernel.org" <keyrings@...r.kernel.org>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-security-module@...r.kernel.org" 
        <linux-security-module@...r.kernel.org>,
        Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>,
        "pvorel@...e.cz" <pvorel@...e.cz>,
        Roberto Sassu <roberto.sassu@...wei.com>,
        "serge@...lyn.com" <serge@...lyn.com>,
        "tiwai@...e.de" <tiwai@...e.de>, Mimi Zohar <zohar@...ux.ibm.com>
Subject: Re: [PATCH 0/7] Add CA enforcement keyring restrictions



> On Nov 4, 2022, at 7:20 AM, Coiby Xu <coxu@...hat.com> wrote:
> 
> Hi Eric,
> 
> I wonder if there is any update on this work? I would be glad to do
> anything that may be helpful including testing a new version of code.
> 
> -- 
> Best regards,
> Coiby


The discussion on this topic briefly moved over to this thread [1].  I took 
the lack of response to mean an approach like this would not be considered.  
If it would be considered, I am willing to continue working on a solution 
to this problem.

1. https://lore.kernel.org/linux-integrity/8BB9D406-0394-4E2E-9B84-4A320AFDBDC4@oracle.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ