From: hiro <firstname.lastname@example.org>
To: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <email@example.com>
Cc: 9fans <firstname.lastname@example.org>
Subject: Re: [9fans] different users for different system roles
Date: Tue, 14 Feb 2023 11:54:13 +0100 [thread overview]
Message-ID: <CAFSF3XOTf-mFugcpqHoeci5X4jfdcAUVyY6La9iitsuVbueEcQ@mail.gmail.com> (raw)
agreed. compartmentalization might be used to have less
users/passwords than servers. if two cpu servers are used
interchangably for the same usecase by the same end-users, why not
give them the same credentials.
next time please try to quote correctly, lyndon.
On 2/14/23, Lyndon Nerenberg (VE7TFX/VE6BBM) <email@example.com> wrote:
> hiro writes:
>> > should each system role get his own user?
>> > Like one user for file servers, one for auth, one for venti, and one for
>> > servers.
> My was has always been to have a file system user and an auth server
> user that are used ONLY for those roles.
> As for CPU servers, it really depends on how you use them. The
> main reason you might want to have different CPU server owners is
> to control access to physical hardware. E.g. I have machines that
> are used to control my radios via their serial and USB interfaces.
> For those, I don't want the "general pupulation" to have access to
> that hardware, so I run those servers under a userid that is distinct
> from the "general purpose" CPU server owner.
> Oh, the Pi I use for bluetooth dev work has its own host owner,
> for similar reasons.
> I'm sure there are other cases, but that's the only one where I've
> personally had a need for multiple host owners.
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2023-02-14 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 8:15 Marco Feichtinger
2023-02-10 9:30 ` Frank D. Engel, Jr.
2023-02-10 11:19 ` hiro
2023-02-14 0:45 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2023-02-14 10:54 ` hiro [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).