News for hackers. Stuff that matters.
Re:Uptime Lab's CM4 Blade Adds NVMe, TPM 2.0 to Raspberry Pi by fakesheriff on Wednesday August 04, 2021 @12:53PM (#28063326)
Without bootloader integration, what's the difference between adding a TPM vs an HSM like [0]? Does TPM just have a more standardized interface?

[0] https://www.zymbit.com/2020/11/10/blog-security-module-raspb...

Re:Uptime Lab's CM4 Blade Adds NVMe, TPM 2.0 to Raspberry Pi by geerlingguy on Wednesday August 04, 2021 @01:05PM (#28063500)
You can actually add both—there's a partial GPIO header for the Zymkey 4i on the board.

But yeah, I think the idea is TPM is a bit more standardized across hardware, so some software that uses it would not need any tweaks to run on the Pi with a TPM built-in.

Re:Uptime Lab's CM4 Blade Adds NVMe, TPM 2.0 to Raspberry Pi by gruez on Wednesday August 04, 2021 @01:23PM (#28063723)
>But yeah, I think the idea is TPM is a bit more standardized across hardware

But there are USB HSMs, along with smart cards (which are also HSMs). Aren't those pretty standard?

Re:Uptime Lab's CM4 Blade Adds NVMe, TPM 2.0 to Raspberry Pi by tadfisher on Wednesday August 04, 2021 @02:01PM (#28064168)
Sort of; the communication protocol is standard (CCID), but the actual HSM interface varies. Yubikeys implement the OpenPGP smartcard interface, for example, as well as PKCS #11.

The TPM specification has its own crypto interface that is standard across all hardware, so you can do things like generate a key and perform crypto operations without requiring the hardware implement a particular interface beyond whatever TPM version you require.

There are advantages and disadvantages to both approaches. On Linux, TPMs are implemented in the kernel, and CCID is handled by userspace drivers.

Re:Uptime Lab's CM4 Blade Adds NVMe, TPM 2.0 to Raspberry Pi by pmorici on Thursday August 05, 2021 @01:32AM (#28070216)
The Zymbit is trying to make up for the lack of secureboot/tpm integration on the Pi by securing the enclosure and monitoring that perimeter.