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: <20200616205732.GF20943@linux.intel.com>
Date:   Tue, 16 Jun 2020 23:57:32 +0300
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Maxim Uvarov <maxim.uvarov@...aro.org>
Cc:     linux-kernel@...r.kernel.org, tee-dev@...ts.linaro.org,
        peterhuewe@....de, jgg@...pe.ca, gregkh@...uxfoundation.org,
        jens.wiklander@...aro.org, linux-integrity@...r.kernel.org,
        arnd@...aro.org, sumit.garg@...aro.org
Subject: Re: [PATCHv8 3/3] tpm_ftpm_tee: register driver on TEE bus

On Thu, Jun 04, 2020 at 08:58:51PM +0300, Maxim Uvarov wrote:
> OP-TEE based fTPM Trusted Application depends on tee-supplicant to
> provide NV RAM implementation based on RPMB secure storage. So this
> dependency can be resolved via TEE bus where we only invoke fTPM
> driver probe once fTPM device is registered on the bus which is only
> true after the tee-supplicant is up and running. Additionally, TEE bus
> provides auto device enumeration.
> 
> Signed-off-by: Maxim Uvarov <maxim.uvarov@...aro.org>
> Suggested-by: Sumit Garg <sumit.garg@...aro.org>
> Suggested-by: Arnd Bergmann <arnd@...aro.org>
> Reviewed-by: Sumit Garg <sumit.garg@...aro.org>

Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>

/Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ