From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: suid bit behaviour modification in 2.6.0-test5
Date: 23 Sep 2003 17:12:59 GMT [thread overview]
Message-ID: <bkpuur$e63$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 200309220425.21862.lkml@ordinal.freeserve.co.uk
In article <200309220425.21862.lkml@ordinal.freeserve.co.uk>,
Ian Hastie <lkml@ordinal.freeserve.co.uk> wrote:
| On Sunday 21 Sep 2003 01:45, Jean-pierre Cartal wrote:
| > Hello,
| >
| > I'm running a standard RH 9 installation upgraded to kernel 2.6.0-test5
| > with rpms from http://people.redhat.com/arjanv/2.5/RPMS.kernel/.
| >
| > I noticed that contrary to what was happening with 2.4.x kernel, suid
| > root files don't loose their suid bit when they get overwritten by a
| > normal user (see example below)
| >
| > Is this the intended behaviour or a bug ?
|
| I got the same results. However it seems the bug is something to do with a
| directory listing cache somewhere. If you sync after copying over the file
| the suid bit is shown as having been cleared.
Well, if ls gets that bit as still set, what would happen if someone
actually ran the program before the sync was done? COuld the file be
modified and then run? Is there a window? Still smells bugish.
|
| $ touch suid_test
|
| # chown root suid_test
| # chmod 4775 suid_test
|
| $ ls -l
| total 0
| -rwsrwxr-x 1 root ianh 0 Sep 22 04:21 suid_test
| $ cp /bin/ls suid_test
| $ ls -l
| total 68
| -rwsrwxr-x 1 root ianh 69228 Sep 22 04:22 suid_test
| $ sync
| $ ls -l
| total 68
| -rwxrwxr-x 1 root ianh 69228 Sep 22 04:22 suid_test
|
| --
| Ian.
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
|
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-09-23 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 0:45 suid bit behaviour modification in 2.6.0-test5 Jean-pierre Cartal
2003-09-22 3:25 ` Ian Hastie
2003-09-23 17:12 ` bill davidsen [this message]
2003-09-23 17:54 ` Andries Brouwer
2003-09-26 22:41 ` Ian Hastie
2003-09-29 3:05 ` Ian Hastie
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='bkpuur$e63$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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