From: bakul at bitblocks.com (Bakul Shah)
Subject: [COFF] The MOO problem and set-uid
Date: Tue, 28 Jan 2020 15:01:31 -0800 [thread overview]
Message-ID: <84453220-427A-45B0-9861-DC63AFFDEF9A@bitblocks.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2001290915500.9191@aneurin.horsfall.org>
The orig. ref. was in the Unix Time Sharing paper. See Section 3.5 near the end.
https://people.eecs.berkeley.edu/~brewer/cs262/unix.pdf <https://people.eecs.berkeley.edu/~brewer/cs262/unix.pdf>
The paper referenced above is behind a paywall (you can see the first page *free of charge*!)
https://onlinelibrary.wiley.com/doi/abs/10.1002/spe.4380010210 <https://onlinelibrary.wiley.com/doi/abs/10.1002/spe.4380010210>
One place the problem is described in some detail:
https://www.cs.unm.edu/~cris/481/gordon-moo.txt <https://www.cs.unm.edu/~cris/481/gordon-moo.txt>:
> On Jan 28, 2020, at 2:18 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
> I recall reading in an old manpage that the (patented) set-uid bit was to solved the MOO problem. I've searched around, but cannot find anything relevant. Anyone know?
>
> -- Dave
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200128/08746f69/attachment.html>
next prev parent reply other threads:[~2020-01-28 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 22:18 dave
2020-01-28 23:01 ` bakul [this message]
2020-01-29 14:50 ` dot
2020-01-30 20:25 ` dave
2020-01-30 21:51 ` bakul
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=84453220-427A-45B0-9861-DC63AFFDEF9A@bitblocks.com \
--to=coff@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).