On my #Librem14 notebook made by #Purism I use #pureboot which includes #heads and #coreboot. I had to replace the ssd.

I also

• upgraded from luks1 to luks2 replacing the key derivation function
• started with a new luks encryption key
• and a new gpg encrypted passphrase
• changed my fs from ext4 to #btrfs

To check for the new key/passphrase whether they work I used this command: /usr/lib/cryptsetup/scripts/decrypt_gnupg-sc /etc/cryptsetup-initramfs/cryptkey.gpg | sudo cryptsetup luksOpen --test-passphrase /dev/nvme0n1p3 && echo yippie-yeah

"UEFI Secure Boot on at least 200 device models from at least 5 major vendors is completely compromised by the leak of their Platform Key."

"it is unlikely that these devices will ever see updates addressing this problem."

"#PureBoot is immune to this type of compromise because it does not have centralized signing keys."

https://puri.sm/posts/purisms-pureboot-is-not-affected-by-uefi-key-leaks-again/

#Purism #FOSS #OpenSource #security

Nitrokey 3 usb-c

https://chrichri.ween.de/articles/a248ad8/nitrokey-3-usb-c

gpg monday

https://chrichri.ween.de/articles/269e88f/gpg-monday

pureboot and rescue system

https://chrichri.ween.de/articles/5742bec/pureboot-and-rescue-system

When we say the #Librem5 is a mobile computer in your pocket, this is what we mean.

One of our customers (@primalmotion) hacks on custom versions of #PureBoot firmware for their #Librem14 which always runs the risk of temporarily bricking your computer.

When that did inevitably happen, they were able to connect their Librem 5 to their hardware flashing equipment and run the same tools you'd run on your Linux laptop to re-flash working firmware.