On Thu, 5 Aug 2021 17:43:46 +0100 Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> wrote: > On Thu, 5 Aug 2021 00:18:35 +0800 > Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> wrote: > > > This is an RFC to start discussions about how we support the Component > > Measurement and Authentication (CMA) ECN (pcisig.com) > > > > CMA provides an adaptation of the data objects and underlying protocol > > defined in the DMTF SPDM specification to be used to authenticate and > > conduct run-time measurements of the state of PCI devices (kind of like > > IMA for devices / firmware). This is done using a Data Object Exchange (DOE) > > protocol described in the ECN. > > > > The CMA ECN is available from the PCI SIG and SPDM can be found at > > https://www.dmtf.org/sites/default/files/standards/documents/DSP0274_1.1.1.pdf > > > > CMA/SPDM is focused on establishing trust of the device by: > > 1) Negotiate algorithms supported. > > 2) Retrieve and check the certificate chain from the device against > > a suitable signing certificate on the host. > > 3) Issue a challenge to the device to verify it can sign with the private > > key associated with the leaf certificate. > > 4) (Request a measurement of device state) > > 5) (Establish a secure channel for further measurements or other uses) > > 6) (Mutual authentication) > > > > This RFC only does steps 1-3 > > > > Testing of this patch set has been conducted against QEMU emulation of > > the device backed by openSPDM emulation of the SPDM protocol. > > Note testing also works with libspdm and libspdm-emu from > https://github.com/DMTF/spdm-emu with no modifications. > > The openSPDM modifications Chris and team made were all associated with the host > end and are not needed for this code (the QEMU part is still needed to provide > the DOE emulation and forward the traffic to spdm_responder_emu) > > I should also have mentioned this series is on top of the recently posted > DOE series rebased onto the linux-cxl next git tree. I'm not really expecting > anyone to test it at this stage, but if desired I can push a full tree out > somewhere with this in place. A couple of updates: 1. This topic is on the agenda for the linaro-open-discussions call tomorrow. https://linaro.atlassian.net/wiki/spaces/LOD/overview It's a public call and anyone interested is welcome to join in. Time is rather unfriendly for US based people unfortunately. I'll throw together some sort of overview / open questions slide deck which will be posted on that page. Note related topics on plumbers microconf agenda later in the month - I'll share details of that once known. 2. Related to that I had a request for trees as the base of the various series are not obvious (involved a bunch of rebases of various other patch sets) https://github.com/hisilicon/kernel-dev/tree/doe-spdm-v1 rebased to 5.14-rc7 https://github.com/hisilicon/qemu/tree/cxl-hacks rebased to qemu/master as of Friday For qemu side of things you need to be running spdm_responder_emu --trans PCI_DOE from https://github.com/DMTF/spdm-emu first (that will act as server to qemu acting as a client). Various parameters allow you to change the algorithms advertised and the kernel code should work for all the ones CMA mandates (but nothing beyond that for now). For the cxl device the snippet of qemu commandline needed is: -device cxl-type3,bus=root_port13,memdev=cxl-mem1,lsa=cxl-mem1, id=cxl-pmem0,size=2G,spdm=true Otherwise much the same as https://people.kernel.org/jic23/ (instructions written to enable testing of the DOE patches this built on). Build at least the cxl_pci driver as a module as we need to poke the certificate into the keychain before that (find the cert in spdm_emu tree). Instructions to do that with keyctl and evmctl are in the cover letter of the patch series. Hopefully I'll find some time soonish to update that blog post with instructions. Thanks, Jonathan > > Jonathan > > > > > https://lore.kernel.org/qemu-devel/1624665723-5169-1-git-send-email-cbrowy@xxxxxxxxxxxxxxxx/ > > > > Open questions are called out in the individual patches but the big ones are > > probably: > > > > 1) Certificate management. > > Current code uses a _cma keyring created by the kernel, into which a > > suitable root certificate can be inserted from userspace. > > > > A=$(keyctl search %:_cma keyring _cma) > > evmctl import ecdsaca.cert.der $A > > > > Is this an acceptable way to load the root certificates for this purpose? > > > > The root of the device provided certificate chain is then checked against > > certificates on this keychain, but is itself (with the other certificates > > in the chain) loaded into an SPDM instance specific keychain. Currently > > there is no safe cleanup of this which will need to be fixed. > > > > Using the keychain mechanism provides a very convenient way to manage these > > certificates and to allow userspace to read them for debug purpose etc, but > > is this the right use model? > > > > Finally the leaf certificate of this chain is used to check signatures of > > the rest of the communications with the device. > > > > 2) ASNL1 encoder for ECDSA signature > > It seems from the openSPDM implementation that for these signatures, > > the format is a simple pair of raw values. The kernel implementation of > > ECDSA signature verification assumes ASN1 encoding as seems to be used > > in x509 certificates. Currently I work around that by encoding the > > signatures so that the ECDSA code can un-encode them again and use them. > > This seems slightly silly, but it is minimum impact on current code. > > Other suggestions welcome. > > > > 3) Interface to present to drivers. Currently I'm providing just one exposed > > function that wraps up all the exhanges until a challenge authentication > > response from the device. This is done using one possible sequence. > > I don't think it makes sense to expose the low level components due to the > > underlying spdm_state updates and there only being a fixed set of valid > > orderings. > > > > Future patches will raise questions around management of the measurements, but > > I'll leave those until I have some sort of implementation to shoot at. > > The 'on probe' use in the CXL driver is only one likely time when authentication > > would be needed. > > > > Note I'm new to a bunch of the areas of the kernel this touches, so have > > probably done things that are totally wrong. > > > > CC list is best effort to identify those who 'might' care. Please share > > with anyone I've missed. > > > > Thanks, > > > > Jonathan > > > > > > Jonathan Cameron (4): > > lib/asn1_encoder: Add a function to encode many byte integer values. > > spdm: Introduce a library for DMTF SPDM > > PCI/CMA: Initial support for Component Measurement and Authentication > > ECN > > cxl/pci: Add really basic CMA authentication support. > > > > drivers/cxl/Kconfig | 1 + > > drivers/cxl/mem.h | 2 + > > drivers/cxl/pci.c | 13 +- > > drivers/pci/Kconfig | 9 + > > drivers/pci/Makefile | 1 + > > drivers/pci/doe.c | 2 - > > include/linux/asn1_encoder.h | 3 + > > include/linux/pci-doe.h | 2 + > > lib/Kconfig | 3 + > > lib/Makefile | 2 + > > lib/asn1_encoder.c | 54 ++ > > lib/spdm.c | 1196 ++++++++++++++++++++++++++++++++++ > > 12 files changed, 1285 insertions(+), 3 deletions(-) > > create mode 100644 lib/spdm.c > > >
