OP-TEE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shyam Saini <shyamsaini@linux.microsoft.com>
To: op-tee@lists.trustedfirmware.org
Subject: [PATCH  v2 0/4] rpmb subsystem, uapi and virtio-rpmb driver
Date: Wed, 31 May 2023 12:10:07 -0700	[thread overview]
Message-ID: <20230531191007.13460-1-shyamsaini@linux.microsoft.com> (raw)
In-Reply-To: <20220405093759.1126835-1-alex.bennee@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Hi Alex,

[ Resending, Sorry for the noise ]
 
Are you still working on it or planning to resubmit it ?

[1] The current optee tee kernel driver implementation doesn't work when IMA is used with optee implemented ftpm.

The ftpm has dependency on tee-supplicant which comes once the user space is up and running and IMA attestation happens at boot time and it requires to extend ftpm PCRs. 

But IMA can't use PCRs if ftpm use secure emmc RPMB partition. As optee can only access RPMB via tee-supplicant(user space). So, there should be a fast path to allow optee os to access the RPMB parititon without waiting for user-space tee supplicant.

To achieve this fast path linux optee driver and mmc driver needs some work and finally it will need RPMB driver which you posted.
 
Please let me know what's your plan on this.
 
[1] https://optee.readthedocs.io/en/latest/architecture/secure_storage.html

Best Regards,
Shyam

       reply	other threads:[~2023-05-31 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220405093759.1126835-1-alex.bennee@linaro.org>
2023-05-31 19:10 ` Shyam Saini [this message]
2023-06-01  1:02   ` [PATCH v2 0/4] rpmb subsystem, uapi and virtio-rpmb driver Zhu, Bing
     [not found] <=?utf-8?q?=3CSN7PR11MB6850DA4A185E3429B62531CD84499=40SN7PR11MB?= =?utf-8?q?6850=2Enamprd11=2Eprod=2Eoutlook=2Ecom=3E?=>
2023-06-01  5:31 ` Ilias Apalodimas
2023-06-13 16:47 ` Shyam Saini
     [not found] < <CAC_iWjKAdimEH0SsC_z9QuFS4sGLp2BVzx03s+RKvcLXY25kuQ@mail.gmail.com>
2023-06-01  5:48 ` Sumit Garg
     [not found] < <CAFA6WYPKeJYTzvnZkoL_dw6uXSkhAh6uxoEOWHYU7oLNRDRWaA@mail.gmail.com>
2023-06-02  8:25 ` Ilias Apalodimas
     [not found] < <CAC_iWjLOhUvp5ggCCkHN5MRNfB_h6FZ2Z14yrtR3aqGn0Ovxig@mail.gmail.com>
2023-06-12 17:06 ` Jens Wiklander
2023-06-13  0:49 ` Shyam Saini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230531191007.13460-1-shyamsaini@linux.microsoft.com \
    --to=shyamsaini@linux.microsoft.com \
    --cc=op-tee@lists.trustedfirmware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox