The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: UNIX version 2*pi
Date: Wed, 18 Oct 2017 06:15:42 -0400	[thread overview]
Message-ID: <085101d347fa$0eae81f0$2c0b85d0$@ronnatalie.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1710181344050.30357@aneurin.horsfall.org>

JHU ownership was a bit more of a kludge.    If your GID was less than 200,
then everything worked the normal UNIX way.
If your GID was greater than 200, then it was also taken to be part of the
UID.   The student accounts would have a GID based on the class that they
were in.

Of course, newgrp, setuid, setgid (and their related bits) had to be changed
to avoid secuirty fun and games.    I spent a lot of time trying to break
that when I was just a student.
When I became one of the system programmers, I spent a lot of time trying to
fix those holes.

-----Original Message-----


We dropped the GID (nobody used them) and glued it onto the UID, thus making
it 16-bit.

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
suffer."



  reply	other threads:[~2017-10-18 10:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 11:58 [TUHS} Running V8 Doug McIlroy
2017-10-16 15:41 ` Don Hopkins
2017-10-17 11:47   ` Tony Finch
2017-10-17 14:30     ` Larry McVoy
2017-10-17 14:50     ` Don Hopkins
2017-10-16 16:28 ` Clem Cole
2017-10-16 16:39   ` [TUHS} Running V8 ... [ really basic tools ] Jon Steinhart
2017-10-16 19:16     ` Ian Zimmerman
2017-10-16 19:28       ` Jon Steinhart
2017-10-17  1:15         ` Ian Zimmerman
2017-10-17  4:20           ` UNIX version 2*pi Don Hopkins
2017-10-17  6:08             ` Dave Horsfall
2017-10-17 18:23               ` Ron Natalie
2017-10-18  2:46                 ` Dave Horsfall
2017-10-18 10:15                   ` Ron Natalie [this message]
2017-10-16 16:38 ` [TUHS} Running V8 Will Senn

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='085101d347fa$0eae81f0$2c0b85d0$@ronnatalie.com' \
    --to=ron@ronnatalie.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).