From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] The MOO problem and set-uid
Date: Wed, 29 Jan 2020 09:18:20 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2001290915500.9191@aneurin.horsfall.org> (raw)
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
next reply other threads:[~2020-01-28 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 22:18 dave [this message]
2020-01-28 23:01 ` bakul
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=alpine.BSF.2.21.9999.2001290915500.9191@aneurin.horsfall.org \
--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).