15 Sep
2020
15 Sep
'20
9:29 p.m.
On Tuesday 15 September 2020 13:48:45 Felmon Davis wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
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
On Tue, 15 Sep 2020, William Morder via trinity-users
wrote:
but this mirrors my situation on my system: I am 'user' and there is
'root'; a lot of things are "out of the user's control" on my
systems
though, of course, I can change my hat and become 'root'.
but maybe that's not what's going on with systemd-homed.
How do you know you're crazy (or even effin crazy)?
In my experience, those few who are really crazy (in the sense
of "out-of-touch with reality") tend to occupy positions of great power and
wealth, especially in government, business and the like.
Do you work in one of those fields? If not, you're probably not as crazy as
you are being told.
Bill
On Tuesday 15 September 2020 11:09:27 Felmon
Davis wrote:
exactly, thank you and apologies to E. Liddell.
On Tue, 15 Sep 2020, Dr. Nikolaus Klepp wrote:
quoted from E.Liddell's earlier post:
###########
The target audience here isn't home users, it's business and education
setups where the users are (understandably) not trusted by the sysadmin.
It's the businesses that pay Red Hat's bills, so naturally they cater to
them. ########### Anno domini 18:08:23 Tue, 15 Sep 2020 +0200
(CEST)
Felmon Davis scripsit:
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. it sounds
like what's terrible about systend-homed is that it's
systemd!
f.
I think Michael's post encapsulated what is wrong with homed (quoting
what he himself mostly quotes):
###########
Quote:
"All user-specific records are stored within a JSON formatted file called
~/.identity which is cryptographically signed with a key out of the users
control."
..."out of the users control"...
Quote-End:
Welcome to Big Brother? Seriously, homed says my data is not mine.
Worse, if homed borks, then
I've lost ALL my data.
This reply from the linked article, also seems to be relevent:
Quote:
gawd, I don't really want to defend a program I don't know or
understand but no, you are supposed to trust *yourself* to know what
your home permissions are.
systemd-homed solves this by doing a chown -R on
the entire home
directory
if there is a conflict.
Riiiiight.
I'm supposed to trust you to know what my home directory permissions are
supposed to be? Are you fucking crazy?"
yes, but now we're off-topic again.
Quote-End:
Background on this is that, especially in a developer's system, it's
frequent to have files owned by different users and groups within your
home. homed is just going to overwrite all that.
###########
thus it seems this is not the intended 'use-case'.
Just trying to bring the different views together
in one place.
thank you, this was helpful, provided context.
f.