From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: landley@webofficenow.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] more SAK stuff
Date: Thu, 5 Jul 2001 21:45:04 -0400 (EDT) [thread overview]
Message-ID: <200107060145.f661j5v74941@saturn.cs.uml.edu> (raw)
In-Reply-To: <01070318005005.06999@localhost.localdomain> from "Rob Landley" at Jul 03, 2001 06:00:50 PM
Rob Landley writes:
> Off the top of my head, fun things you can't do suid root:
...
> ps (What the...? Worked in Red Hat 7, but not in suse 7.1.
> Huh? "suid-to apache ps ax" works fine, though...)
The ps command used to require setuid root. People would set the
bit by habit.
> I keep bumping into more of these all the time. Often it's fun
> little warnings "you shouldn't have the suid bit on this
> executable", which is frustrating 'cause I haven't GOT the suid bit
> on that executable, it inherited it from its parent process, which
> DOES explicitly set the $PATH and blank most of the environment
> variables and other fun stuff...)
Oh, cry me a river. You can set the RUID, EUID, SUID, and FUID
in that same parent process or after you fork().
Since you didn't set all the UID values, I have to wonder what
else you forgot to do. Maybe you shouldn't be messing with
setuid programming.
next prev parent reply other threads:[~2001-07-06 1:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 12:16 [PATCH] more SAK stuff Andries.Brouwer
2001-07-02 12:33 ` Alan Cox
2001-07-02 19:10 ` Hua Zhong
2001-07-03 22:00 ` Rob Landley
2001-07-06 1:45 ` Albert D. Cahalan [this message]
2001-07-06 10:04 ` The SUID bit (was Re: [PATCH] more SAK stuff) Rob Landley
2001-07-06 15:17 ` Doug McNaught
2001-07-06 15:44 ` Rob Landley
2001-07-02 18:57 ` [PATCH] more SAK stuff Kain
2001-07-06 22:02 ` David Wagner
2001-07-02 12:49 Andries.Brouwer
2001-07-02 13:03 Andries.Brouwer
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=200107060145.f661j5v74941@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=landley@webofficenow.com \
--cc=linux-kernel@vger.kernel.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).