From: random832@fastmail.us (random832@fastmail.us)
Subject: [TUHS] success, bj assembled and linked in Unix v5
Date: Sat, 13 Jun 2015 22:50:24 -0400 [thread overview]
Message-ID: <1434250224.3528778.294918977.25E8E029@webmail.messagingengine.com> (raw)
In-Reply-To: <20150614014155.GC20321@mercury.ccil.org>
On Sat, Jun 13, 2015, at 21:41, John Cowan wrote:
> But it won't be owned by the original owner, which means any setuid bit
> will give it the permissions of the copy-maker.
Right, but 744 doesn't include a setuid bit.
next prev parent reply other threads:[~2015-06-14 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 1:08 Norman Wilson
2015-06-14 1:41 ` John Cowan
2015-06-14 2:50 ` random832 [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 20:51 Noel Chiappa
2015-06-12 20:33 Mark Longridge
2015-06-12 20:57 ` cowan
2015-06-12 21:01 ` Ronald Natalie
2015-06-12 22:23 ` Mark Longridge
2015-06-13 17:48 ` Dave Horsfall
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=1434250224.3528778.294918977.25E8E029@webmail.messagingengine.com \
--to=random832@fastmail.us \
/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).