tang VS build-meta

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.

I found that running tang[1] at home and needing to decrypt that box (can be a Pi or whatever) requiring a complex passphrase is very sufficient. You can even just unplug it at night if it makes you sleep better.

https://github.com/latchset/tang

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

This is why on headless servers you use tang (ideally, multiple tang servers)

Sharing my notes on running a Tang server on OPNSense, in case it is useful for somebody else.

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.

For automating unlocking of encrypted drives, look into tang . Here is a red hat guide on setting it up. You will want to be running this on another device on your network, i run it on my router with openwrt since its a local device thats on 24/7. Basically it will unlock your disks as long as your server is on your network, so if your machine or drives are stolen or removed from your network they will just be encrypted as usual. Obviously use a strong encryption password.

There are other ways to bind data, e.g. "network binding" with Tang server.

I wonder if https://github.com/latchset/clevis and https://github.com/latchset/tang (complementary projects) will help here.

Yes you can, using either Mandos or Clevis and Tang. https://www.recompile.se/mandos https://github.com/latchset/clevis https://github.com/latchset/tang. Basically on boot the server gets the key from another(s) servers. You could use a hidden raspberry pi for example.

Tracking issue: https://gitlab.com/carbonOS/build-meta/-/issues/140

"Re-created the install media" seems to imply you're building carbonOS yourself. Make sure your git checkout is newer than this commit: https://gitlab.com/carbonOS/build-meta/-/commit/f6a8db8af00808e8bacd3334952baff10487e49f. I suggest you just build off of the gnome branch. If you're building carbonOS, please check out the carbonOS Development Matrix channel: #carbonOS-devel:matrix.org

I'm working on one of those new-fangled atomic distros and I've been planning on how to actually securely verify every bit of OS data that loads and simultaneously keep every bit of user data encrypted. If you're interested, here's my tracking issue where I keep plans on how to best lock everything down: https://gitlab.com/carbonOS/build-meta/-/issues/44

The main source for the actual OS is here: https://gitlab.com/carbonOS/build-meta