udiskie VS clevis

The most common approach (though a bit different) to get write access for users is probably using udisks[1]/udiskie[2] which use udev and polkit [3]. udiskie even supports luks unlocking [4].

https://github.com/coldfix/udiskie looks close, but does it work without desktop environments? Is there alternatives to udiskie that doesn't require desktop environments and supports unlocking LUKS encrypted volumes?

Based on https://github.com/coldfix/udiskie/blob/master/doc/udiskie.8.txt and https://github.com/coldfix/udiskie/issues/66#issuecomment-289204539, you probably need to create a configuration for the encrypted hard disk in the file ~/.config/udiskie/config.yml. For example, as follows.

For example, I typically ran things like lxpolkit, nm-applet, redshift, udiskie and xfce4-power-manager when I used i3.

By running udiskie in your i3 session, for example.

This. There is also udiskie, a GUI tool with notification icon, support for unlocking encrypted partitions, powering off USB devices, and so on.

I've used udiskie to handle removable drives in i3.

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.