[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201204051642.GA154469@kernel.org>
Date: Fri, 4 Dec 2020 07:16:42 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
James Bottomley <jejb@...ux.ibm.com>,
David Howells <dhowells@...hat.com>,
Jens Wiklander <jens.wiklander@...aro.org>,
Jonathan Corbet <corbet@....net>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Casey Schaufler <casey@...aufler-ca.com>,
Janne Karhunen <janne.karhunen@...il.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Markus Wamser <Markus.Wamser@...ed-mode.de>,
Luke Hinds <lhinds@...hat.com>,
"open list:ASYMMETRIC KEYS" <keyrings@...r.kernel.org>,
linux-integrity@...r.kernel.org,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
op-tee@...ts.trustedfirmware.org
Subject: Re: [PATCH v8 0/4] Introduce TEE based Trusted Keys support
On Fri, Nov 06, 2020 at 04:52:52PM +0200, Jarkko Sakkinen wrote:
> On Fri, Nov 06, 2020 at 03:02:41PM +0530, Sumit Garg wrote:
> > On Thu, 5 Nov 2020 at 10:37, Jarkko Sakkinen <jarkko@...nel.org> wrote:
> > >
> > > On Tue, Nov 03, 2020 at 09:31:42PM +0530, Sumit Garg wrote:
> > > > Add support for TEE based trusted keys where TEE provides the functionality
> > > > to seal and unseal trusted keys using hardware unique key. Also, this is
> > > > an alternative in case platform doesn't possess a TPM device.
> > > >
> > > > This patch-set has been tested with OP-TEE based early TA which is already
> > > > merged in upstream [1].
> > >
> > > Is the new RPI400 computer a platform that can be used for testing
> > > patch sets like this? I've been looking for a while something ARM64
> > > based with similar convenience as Intel NUC's, and on the surface
> > > this new RPI product looks great for kernel testing purposes.
> >
> > Here [1] is the list of supported versions of Raspberry Pi in OP-TEE.
> > The easiest approach would be to pick up a supported version or else
> > do an OP-TEE port for an unsupported one (which should involve minimal
> > effort).
> >
> > [1] https://optee.readthedocs.io/en/latest/building/devices/rpi3.html#what-versions-of-raspberry-pi-will-work
> >
> > -Sumit
>
> If porting is doable, then I'll just order RPI 400, and test with QEMU
> up until either I port OP-TEE myself or someone else does it.
>
> For seldom ARM testing, RPI 400 is really convenient device with its
> boxed form factor.
I'm now a proud owner of Raspberry Pi 400 home computer :-)
I also found instructions on how to boot a custom OS from a USB stick:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
Also, my favorite build system BuildRoot has bunch of of the shelf
configs:
➜ buildroot-sgx (master) ✔ ls -1 configs | grep raspberry
raspberrypi0_defconfig
raspberrypi0w_defconfig
raspberrypi2_defconfig
raspberrypi3_64_defconfig
raspberrypi3_defconfig
raspberrypi3_qt5we_defconfig
raspberrypi4_64_defconfig
raspberrypi4_defconfig
raspberrypi_defconfig
I.e. I'm capable of compiling kernel and user space and boot it up
with it.
Further, I can select this compilation option:
BR2_TARGET_OPTEE_OS: │
│
OP-TEE OS provides the secure world boot image and the trust │
application development kit of the OP-TEE project. OP-TEE OS │
also provides generic trusted application one can embedded │
into its system. │
│
http://github.com/OP-TEE/optee_os
Is that what I want? If I put this all together and apply your patches,
should the expectation be that I can use trusted keys?
Please note that I had a few remarks about your patches (minor but need
to be fixed), but this version is already solid enough for testing.
/Jarkko
Powered by blists - more mailing lists