From: Chet Ramey via TUHS <tuhs@tuhs.org>
To: Rik Farrow <rik@rikfarrow.com>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: "Webster's Second on the Head of a Pin"?
Date: Thu, 2 Jan 2025 14:47:26 -0500 [thread overview]
Message-ID: <17895df2-19e5-45a0-aa7b-68af93522396@case.edu> (raw)
In-Reply-To: <CACY3YMHty5T3mHgTADKuCEo8vcPVD7XMhszqbYYFbCE2t8JuWA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1389 bytes --]
On 1/2/25 1:13 PM, Rik Farrow wrote:
>
>
> On Thu, Jan 2, 2025 at 7:23 AM Chet Ramey <chet.ramey@case.edu
> <mailto:chet.ramey@case.edu>> wrote:
>
> On 1/1/25 1:11 PM, Rik Farrow wrote:
> > For example, the 3B2 I
> > administered for a while in the late 80s had multiple accounts with
> rsh,
> > the restricted shell, as the login shell. That was okay, unless you
> used su
> > and then had access to a root shell.
>
> That's an administrator problem. Part of setting up a restricted shell
> environment is creating a directory of necessary binaries and setting
> PATH appropriately.
>
> Each of these special accounts did have a home directory with a .profile to
> set up the restricted environment, then run a shell script to perform some
> task as root. For example, logging in as 'backup' would run /user/
> backup/.profile and allow a non-privileged user to run a backup script as root.
>
> But typing "su backup" produced a root-owner shell without restrictions.
> You need to type "su - " to run the account's .profile script.
OK, I thought you meant the other way, breaking out of a restricted
environment.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2025-01-02 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 2:53 [TUHS] " Royce Williams
2024-12-29 13:44 ` [TUHS] " Douglas McIlroy
2024-12-30 21:13 ` sjenkin
2024-12-31 16:37 ` Chet Ramey via TUHS
2025-01-01 15:02 ` Douglas McIlroy
2025-01-01 18:11 ` Rik Farrow
2025-01-02 3:05 ` Douglas McIlroy
2025-01-02 14:28 ` Chet Ramey via TUHS
2025-01-02 14:22 ` Chet Ramey via TUHS
2025-01-02 18:13 ` Rik Farrow
2025-01-02 19:47 ` Chet Ramey via TUHS [this message]
2024-12-29 16:05 ` Douglas McIlroy
2025-03-10 22:55 ` James Johnston
2025-03-11 0:23 ` Douglas McIlroy
2025-03-11 14:47 ` Jeff Johnson
2025-03-12 12:41 ` Douglas McIlroy
2024-12-30 0:37 ` Warren Toomey via TUHS
2024-12-30 2:07 ` Royce Williams
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17895df2-19e5-45a0-aa7b-68af93522396@case.edu \
--to=tuhs@tuhs.org \
--cc=chet.ramey@case.edu \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=rik@rikfarrow.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).