modem_down, modem_down@thebrainbin.org

their setup required a couple large antennas that the victim would need to stand in between. Not impossible, but you’d notice with each side being half a meter away.

So yes, it’s a technical risk, but not one that I’d bother putting much effort into avoiding. And the being able to use the key via NFC is probably worth the risk.

This was my conclusion, too, but I didn’t want to prejudice the discussion. Thanks for corroborating.

IMO, using a Faraday pouch isn’t “much effort”, and is therefore worth doing if the HST is being carried in unfamiliar/non-secure locations.

Interesting point. Would realistic human-edited ("Photoshopped") content have to be labelled? That could be a good thing!

(Might cause embarrassment for fashion magazines unless they stop doing it.)

Even if you can [exploit NFC] at 1m, thats close enough that it can just be stolen from you.

Stealing the HST should not give the user a false sense of security. Not so dangerous.

Silently exfiltrating the private key (or data for a replay attack), OTOH, would leave the user with a false sense of security. Dangerous.

your link to rfidgate appears broken

Wfm. Here’s an archive link.

If it’s a server for self hosting you definitely don’t want anything that requires interaction at boot.

Depends on use-case. If you only plan to boot it when you’re physically present, it’s fine.

i believe a much better secure layer is something similar to what Novacustoms, Purism attempt to do: verify if somebody else not you try to access the laptop.

You’re thinking of Heads, which I agree is ideal for supported motherboards.

tang

Thanks. TIL about Clevis/Tang.

I read them before writing my OP. I’m still not sure what you’re getting at.

I would be grateful if you could say what you mean, instead of initiating an oblique guessing game.

Yes. Here are some common self-hosting scenarios:

• Home server containing family files: scans, photos, device backups, …
• Office server containing business files: sensitive documents, device backups, …
• Web or email server containing websites, Fediverse instances, emails, etc

In all those cases, full disk encryption (FDE) is a sensible precaution to protect the data in case the server is physically stolen.

Linux is probably the most common OS kernel for self-hosting. On Linux, LUKS (Linux Unified Key Setup) is probably the best FDE system. It’s mature and reliable. But anyone self-hosting a Linux server with LUKS FDE is faced with the question of where to store the keys.

Hardware security tokens (HSTs) are widely considered a safer place for keys than SSDs, HDDs, or USB storage. They follow the smartcard principle: a private key can be written to an HST but not read from it (security vulnerabilities excepted). Instead, they implement cryptographic algorithms to prove possession of the private key. So, anyone self-hosting a Linux server with LUKS FDE should strongly consider storing their private key(s) on an HST.

However, there is more than one way to do that. Hence the question in my OP.

Which of the 4 recipes I posted are you referring to as “this”?

Thanks, please post relevant steps if you have specific recommendations.

Many thanks for this clarification - and for hosting The Brain Bin!