From: Shyam Saini <shyamsaini@linux.microsoft.com>
To: op-tee@lists.trustedfirmware.org
Subject: [v2,0/4] rpmb subsystem, uapi and virtio-rpmb driver
Date: Mon, 29 May 2023 23:23:36 +0000 [thread overview]
Message-ID: <ef44fb8e-7b31-96a7-2ce0-302f11bbbdc2@linux.microsoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
Hi Alex,
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 the 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
Thanks,
Shyam
reply other threads:[~2023-05-29 23:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ef44fb8e-7b31-96a7-2ce0-302f11bbbdc2@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