3 ms·
I thought one of the big selling points for this was the ability to move the homedirectory from one device to another via usb or hdd? Then how will they verifi
by bpfrh 7y ago
I thought one of the big selling points for this was the ability to move the homedirectory from one device to another via usb or hdd?
Then how will they verifiy the signature of the user json file?
So I can't simply remount the user profile on another system?
Seems like a step back.
- Aardwolf 7y ago> I thought one of the big selling points for this was the ability to move the homedirectory from one device to another via usb or hdd? I've been able to do this for decades, just copy the files. Why would I want systemd for that? systemd has already made my textual log files binary and only accessible with their own viewer. Now it's going to apply its philosophy to my home directory too?
- Spivak 7y agoYou have a pendrive containing your encrypted home directory and you can plug this drive in to a machine that doesn't a priori have your user account info and log in to your account without administrative privilege. This could genuinely be a viable lightweight alternative to LDAP/IPA in offices that hotdesk. Just sign the user's drive once and they can plug-in to any workstation.
- qu4z-2 7y agoI don't really understand why they bother to encrypt it if you're going to be typing your password into presenter laptops, etc...
- Spivak 7y agoBecause someone who steals your drive can’t decrypt it? How could you possibly design a system where you can plug a drive into an openly hostile machine, decrypt and use it, and have that machine not be able to access your password or files?
- Aardwolf 7y agoIsn't that already possible with a LUKS container?
- Spivak 7y agoWell yes, systemd-homed uses LUKS containers for the encryption format. This project is all about the tooling to support pluggable users.