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:   Mon, 11 Oct 2021 12:19:19 +0200
From:   Ahmad Fatoum <>
To:     Andreas Rammhold <>,
        Mimi Zohar <>,
        David Howells <>,
        Jarkko Sakkinen <>,
        James Bottomley <>
Cc:     James Morris <>,
        "Serge E. Hallyn" <>,
        Sumit Garg <>,,,,
Subject: Re: [PATCH v3] KEYS: trusted: Fix trusted key backends when building
 as module

Hello Mimi, David, Jarkko and James,

On 02.10.21 23:47, Andreas Rammhold wrote:
>> My mistake.  Trusted and encrypted key types have always been defined
>> as tristate.  Only when EVM selects encrypted keys, and by extension
>> trusted keys, are they builtin.
> So how do we go about this patch? Building the TPM support as module has
> broken actually using the trusted backend. This patch fixes that while
> still allowing it to be a builtin. If there is some configuration there
> a module isn't acceptable I am sure that is handled within Kconfig?
Can anyone of you four pick this up? Andreas' regression fix has
had Jarkko's Reviewed-by for close to two months and a half now.


Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Powered by blists - more mailing lists