It all seems reasonable to me. Linux home directories are a bit of a mess and unportable.
Can someone explain to me the hate for systemd other than: "It's trying to do too much" "I hate Poettering" "I prefer things to stay the same, that's why I use a ThinkPad from 2008"
These are their identified problems:
Needs writable /etc + Mixes State and Con guration
UID assignments need to be propagated between systems
No encryption (Or \mismatching" encryption)
No modern authentication mechanisms
Not extensible; plenty \Sidecar" databases (/etc/shadow,
accounts-daemon, samba, SSH, pam limits) No resource management
These are their stated goals: Migratable Home Directories (all the way to the point of
\home-on-a-stick") Self Contained Home Directories (i.e. mere existance of a le
/home/foobar.home synthesizes a user foobar) UID assignments as local artifact
Unification of User Password and Encryption Key
Extensible User Records
Lock LUKS on System Suspend
Yubikeys, from day #1
"Complications:* SSH Logins
Disk Space Assignments
UID Assignments (chown() on login)
LUKS Locking
They have two solutions:Concept A: JSON User Records
(Superset of NSS records: struct passwd + struct group)
Queriable via Varlink interface
Convertible forth and back (lossy though, necessarily)
Concept B Encrypted LUKS Home Directories in Loopback Files
(/home/foobar.home with JSON records in ~/.identity)
Managed by systemd-homed.service
Concept A may be used without Concept B though