From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Set-uid shell scripts
Date: Sun, 04 Aug 2019 17:18:45 -0400 [thread overview]
Message-ID: <1564953528.6352.for-standards-violators@oclsc.org> (raw)
Noel Chiappa:
I wonder why it passed the link name, instead of the actual filename of the
target (script)? Perhaps to allow one script to have multiple functions,
depending on the name it was called with?
====
In fact the latter is still used here and there in standard
system distributions.
But from a security viewpoint it doesn't matter. For
ln -s /bin/scriptname ./-i
substitute
execl("/bin/scriptname", "-i", (char *)0);
If you can execute a program, you can fake its arguments,
including argv[0]. There is no defence.
Norman Wilson
Toronto ON
next reply other threads:[~2019-08-04 21:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 21:18 Norman Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 0:13 Noel Chiappa
2019-08-04 21:27 Norman Wilson
2019-08-06 8:28 ` jason-tuhs
2019-08-06 9:55 ` arnold
2019-08-06 22:48 ` Dave Horsfall
2019-08-06 22:56 ` ron minnich
2019-08-07 1:21 ` Dave Horsfall
[not found] ` <40c92e85142fe7e3@orthanc.ca>
2019-08-07 21:33 ` Dave Horsfall
2019-08-08 6:39 ` Peter Jeremy
2019-08-07 12:56 ` Chet Ramey
2019-08-07 21:40 ` Dave Horsfall
2019-08-08 5:16 ` Adam Thornton
2019-08-14 5:41 ` Efton Collins
2019-08-04 20:18 Noel Chiappa
2019-08-04 20:29 ` Clem Cole
2019-08-04 20:42 ` Richard Salz
2019-08-04 23:58 ` Dave Horsfall
2019-08-04 7:36 Dave Horsfall
2019-08-04 7:43 ` Alec Muffett
2019-08-04 15:58 ` Noel Chiappa
2019-08-04 16:30 ` Michael Kjörling
2019-08-04 16:48 ` Alec Muffett
2019-08-04 17:48 ` Michael Kjörling
2019-08-04 19:45 ` Alec Muffett
2019-08-04 16:50 ` Rico Pajarola
2019-08-04 7:46 ` arnold
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=1564953528.6352.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--cc=tuhs@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).