On Tue, 15 Sep 2020, Dr. Nikolaus Klepp wrote:
Anno domini 18:08:23 Tue, 15 Sep 2020 +0200 (CEST)
Felmon Davis scripsit:
[...]
I take it with systemd-homed one doesn't get trapped by shifting UIDs
and such. they write (partial quotation),
"Linux assigns UIDs in the order usernames are registered on a
machine. you may get UID 1000 if you are the first user on a laptop
and you could get 1001 on another laptop if you are the second user to
be registered there. This poses a problem if you move a home directory
container from machine A where you're UID 1000 to machine B where you
are 1001. systemd-homed solves this by doing a chown -R on the entire
home directory if there is a conflict. [...]"
I once fell athwart of that! not to mention that 'home' gets encrypted.
why isn't this a net bonus?
There are hords of resons.
many of the reasons you cite go beyond my technical knowledge but I'll
venture comments on a couple:
1) security relies on trust into the computer you plug your home in.
Well, that's a bad plan to begin with. System is compromised, sor
your home is now compromised, too. And becaus of the ease to do, you
compromomise all systems you go to that day and the next day ...
I guess it depends on the intended use-case. if I want to transfer
'home' to another one of my computers, there is no problem or rather,
I already had a problem if the computer I'm transferring to is
compromised.
and as someone pointed out further down-thread (sorry, I can't find
the msg!) this may be suitable to a business environment.
2) TRhis problem was solved when? 40 years ago? When was it, NFS+yellowpages was introduced?
I have no idea. will have to look this up.
sometime.
3) It does not address at all the problems of different hardware and
different OS. You can share your home on any *nix system you like -
if you are a bit coutious - without systemd-homed. You cannot any
more when you use systemd-homed.
I don't follow. even rsync-ing to another computer may involve some
fix-ups as Kate expressly indicated. you are saying once installed by
'systemd-homed' I cannot fix configuration files in 'home'?
4) WTF encrypted JSON? This is soooo systemd. Remember the "benefits" of binary logfiles?
5) "systemd-homed" looks more like "systemd-owned" than anything else.
Nik
I don't use systemd or at least didn't until it cropped up in my
install of MX and 4QOS but I think that's minimalistic.
anyway, I'm not advocating systemd, just wondering what's so terrible
about systemd-homed.
it sounds like what's terrible about systend-homed is that it's
systemd!
f.
--
Felmon Davis
Verbum sat sapienti.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
