From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: Rik Farrow <rik@rikfarrow.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: "Webster's Second on the Head of a Pin"?
Date: Wed, 1 Jan 2025 22:05:38 -0500 [thread overview]
Message-ID: <CAKH6PiWRdQ0kxF6HAvrebnBccu97d1kudsFyn=KZCtOVcPR3Qw@mail.gmail.com> (raw)
In-Reply-To: <CACY3YMFNWAVh+8_pHSrU7oxY4ouuAAW06Jh+fFv3PQxFmBLk5w@mail.gmail.com>
I think $IFS ranks at the top of Jim's cabinet of horrors. For our
multilevel-secure Unix (https://www.cs.dartmouth.edu/~doug/IX), he
took almost everything out of the administrative shell, nosh (the
no-shell shell), The classic /bin/sh was not endowed with any of the
capabilities necessary to override Bell-LaPadula-Biba secrecy or
integrity constraints.
On Wed, Jan 1, 2025 at 1:11 PM Rik Farrow <rik@rikfarrow.com> wrote:
>
> I wonder what Reeds meant. I know there are issues. 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.
>
> HP/UX was way worse, with over 120 SUID shell scripts in the 90s. A much more interesting example of insecurity. But somehow, I'm guessing that's not what Reeds wrote about.
>
> Rik
>
>
> On Wed, Jan 1, 2025 at 8:02 AM Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
>>
>> I have it and will try to scan it in the next few days. Bug me if it
>> doesn't appear.
>>
>> Doug
>>
>> On Tue, Dec 31, 2024 at 11:37 AM Chet Ramey <chet.ramey@case.edu> wrote:
>> >
>> > On 12/29/24 8:44 AM, Douglas McIlroy wrote:
>> > > I can supply a copy if no one else has beaten me to it.
>> > >
>> > > Ron Hardin subsequently pushed the limit even further. Unfortunately,
>> > > I do not have a record of that work.
>> >
>> > Along these same lines, does anyone on the list have a copy of
>> >
>> > "J. A. Reeds, /bin/sh: The biggest UNIX security Loophole,
>> > 11217-840302-04TM, AT&T Bell Laboratories, Murray Hill, NJ (1984)"?
>> >
>> > Years ago, in another lifetime, I wrote and asked him for a copy, but
>> > never got a reply.
>> >
>> > --
>> > ``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/
next prev parent reply other threads:[~2025-01-02 3:06 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 [this message]
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
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='CAKH6PiWRdQ0kxF6HAvrebnBccu97d1kudsFyn=KZCtOVcPR3Qw@mail.gmail.com' \
--to=douglas.mcilroy@dartmouth.edu \
--cc=rik@rikfarrow.com \
--cc=tuhs@tuhs.org \
/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).