clevis VS cryptsetup

Recently learned that Clevis also supports Shamir Secret Sharing, and it's in fact the only way to configure multiple pins even if they're of the same type and authority (ie. the RAID0 of SSS):

https://github.com/latchset/clevis#pin-shamir-secret-sharing

Have a look at clevis and tang. These allow you do have one server - which could be your remote you want to pull from - to be source of the LUKS decryption on the system using tang.

Interesting question. I think so?

https://access.redhat.com/documentation/en-us/red_hat_enterp...

Looks like clevis is gpl3 - so I expect it's not packaged as standard for any of the bsds?

https://github.com/latchset/clevis

See also:

https://security.stackexchange.com/questions/194081/use-tpm2...

https://security.stackexchange.com/questions/39329/how-does-...

https://superuser.com/questions/619721/can-i-use-the-tpm-on-...

I haven't used it myself, but a solution with LUKS, TPM2, and clevis is the way I've seen other people set it up https://github.com/latchset/clevis

There are 3 ways to unlock a volume in a headless environment: - use a keyfile, located on an already available volume - use your device's TPM and utilize systemd-cryptenroll - use Clevis/Tang to unlock volumes remotely

I don't think there is a turnkey solution, but you can build what you are looking for with clevis, LUKS, and dm-crypt

We use clevis against multiple tang servers to provide Network Bound Disk Encryption (NBDE). It's possible to also use TPM2 but it's easier to use multiple tang servers (requiring more than one server to decrypt) in the datacenter.

Overall, “dm-crypt” is a device-mapper target (https://elixir.bootlin.com/linux/v6.5-rc3/source/drivers/md/dm-crypt.c#L3689) supported from kernel version 2.6.4 (https://elixir.bootlin.com/linux/v2.6.4/source/drivers/md/dm-crypt.c). It is responsible for transparent (aka real-time/on-the-fly encryption) block device encryption while using the kernel crypto API (https://gitlab.com/cryptsetup/cryptsetup/-/wikis/DMCrypt) .

For more information check section 5.21 Why is there no "Nuke-Option"? of LUKS FAQ.

Please read the section 5.21 Why is there no "Nuke-Option"? of the LUKS FAQ for more information (eg. when a "wipe" option could actually harm you).

Check out the section 5.2 and 5.18 of the LUKS FAQ for more information.

See section 5.2 of LUKS FAQ and Key disclosure law all over the world.

References: - Frequently Asked Questions Cryptsetup/LUKS - Question 2.15: "neither dm-crypt nor LUKS1 stores partition size and LUKS2 uses a generic "whole device" size as default." - Stackexchange: What does cryptsetup resize do if LUKS doesn't store partition size?

LUKS is probably what you want