@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃

- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped).

Joe Richey released #fscrypt version 0.3.6. https://github.com/google/fscrypt
GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption

Go tool for managing Linux filesystem encryption. Contribute to google/fscrypt development by creating an account on GitHub.

GitHub

I wonder how fscrypt compares to LUKS. It does encryption at the filesystem level instead of underneath it at the block device level.

Apparently XTS (which block device encryption uses out of necessity) isn't great at least according to https://sockpuppet.org/blog/2014/04/30/you-dont-want-xts/, and fscrypt would solve that. But fscrypt also leaks a bunch of metadata that LUKS doesn't.

It sounds like Android's encryption is fscrypt-based? So Google at least thinks it's good enough for them. But I worry if we did it ourselves we'd misuse it somehow.

#linux #LUKS #fscrypt #cryptography

You Don't Want XTS — Quarrelsome

#askfedi To my fellow nerds out there, is #btrfs not properly compatible with #fscrypt on #Fedora 42 using #systemd-homed yet or did I just fuck something up? Luks works well and is more secure because it encrypts metadata but I really wanted to try dynamic encrypted home directories.
Joe Richey released #fscrypt version 0.3.5. https://github.com/google/fscrypt
GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption

Go tool for managing Linux filesystem encryption. Contribute to google/fscrypt development by creating an account on GitHub.

GitHub

#FSCRYPT In Linux 6.7 More Adaptable For Inline Encryption Hardware

https://www.phoronix.com/news/Linux-6.7-FSCRYPT

FSCRYPT In Linux 6.7 More Adaptable For Inline Encryption Hardware

Joe Richey released #fscrypt version 0.3.3. https://github.com/google/fscrypt
GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption

Go tool for managing Linux filesystem encryption. Contribute to google/fscrypt development by creating an account on GitHub.

GitHub

Sweet Tea Dorminy submitted an patch-set adding an encryption feature to #btrfs: https://lore.kernel.org/all/cover.1687[email protected]/

```This is a changeset adding encryption to btrfs. It is not complete; it does not support inline data or verity or authenticated encryption. It is primarily intended as a proof that the fscrypt extent encryption changeset it builds on work.```

For the mentioned #fscrypt changes see:
https://lore.kernel.org/linux-fscrypt/[email protected]/ #Linux #kernel #LinuxKernel

[PATCH v1 00/17] btrfs: add encryption feature - Sweet Tea Dorminy

Hm, interesting, #fedora seems to be moving to full-disk-encryption using #btrfs and #fscrypt by default, along with signing unified kernel images (UKIs) and using the #TPM. No measuring/attestation AFAICT yet, but a very good move forward!

They also want to separately encrypt homes, and even mention #systemd #homed in the Pagure:
https://pagure.io/fedora-workstation/blob/master/f/notes/encryption.md
However they write:

> *It cannot be universal for all Fedora systems - some things like NFS home directories are out of scope for systemd-homed. Logging in remotely via ssh is not supported. (???)*

I'm pretty sure ssh is supported and even documented, and #NFS should be of no business to homed? But NFS+automount should work perfectly fine with #homed, or did I misunderstand something?

Maybe someone with more knowledge than me should chip in, otherwise they will re-invent the wheel (and doing separately encrypted homes is hard to do correctly!)

Tree - fedora-workstation - Pagure.io

Joe Richey released #fscrypt version 0.3.4. https://github.com/google/fscrypt
GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption

Go tool for managing Linux filesystem encryption. Contribute to google/fscrypt development by creating an account on GitHub.

GitHub