From: "Ron Natalie" <ron@ronnatalie.com>
To: "TUHS main list" <tuhs@minnie.tuhs.org>
Subject: [TUHS] Speaking of groups: JHU Ownership
Date: Tue, 16 Nov 2021 16:43:23 +0000 [thread overview]
Message-ID: <em7feeedaf-fffb-4065-87bb-e3abca7a199f@alien> (raw)
In-Reply-To: <CAC20D2OT6ZcFOqnNCkqDUfAKy87wYu7mp7xx0ozzAT0eN1wr8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
A private message with Uh, Clem reminds me of another quaint piece of
UNIX group history: JHU Ownership.
The original V6 kernel and file systems used a char for UID and GID.
This meant that you could only have 255 (plus the root user) distinct
users on the machine. The JHU PDP-11/45 was used for the EE classes
and we had more than that many users. The kernel was modified to
check if the GID was 200 or greater. If it was, that was taken along
with the UID to be part of the user identity. We gave all the class
accounts such GIDs.
Of course, we had to be careful about newgrp and fun and games with
setuid/setgid (both the system call and the bits on the executables).
I spent a lot of my time looking for exploits there and fixing them once
I (or someone else) found them.
[-- Attachment #2: Type: text/html, Size: 1665 bytes --]
next prev parent reply other threads:[~2021-11-16 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 3:16 [TUHS] Book Recommendation Douglas McIlroy
2021-11-16 4:08 ` G. Branden Robinson
2021-11-16 14:56 ` Clem Cole
2021-11-16 15:37 ` Richard Salz
2021-11-16 15:50 ` Adam Thornton
2021-11-16 16:02 ` [TUHS] BASIC, RSTS, and UNIX Ron Natalie
[not found] ` <CAC20D2OT6ZcFOqnNCkqDUfAKy87wYu7mp7xx0ozzAT0eN1wr8g@mail.gmail.com>
2021-11-16 16:43 ` Ron Natalie [this message]
2021-11-16 17:02 ` [TUHS] Book Recommendation Will Senn
2021-11-16 21:38 ` John Cowan
2021-11-16 21:46 ` Will Senn
2021-11-16 18:27 ` Jon Steinhart
2021-11-16 18:44 ` Heinz Lycklama
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=em7feeedaf-fffb-4065-87bb-e3abca7a199f@alien \
--to=ron@ronnatalie.com \
--cc=tuhs@minnie.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).