From: Chris Evans <chris@scary.beasts.org>
To: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
Cc: chris@scary.beasts.org, linux-kernel@vger.kernel.org, drepper@redhat.com
Subject: Re: [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch
Date: Tue, 29 Oct 2002 11:18:22 +0000 [thread overview]
Message-ID: <E186UO6-0000sD-00@sphinx.mythic-beasts.com> (raw)
In-Reply-To: <877kg2njbi.fsf@goat.bogus.local>
Hi,
Quoting Olaf Dietsche
<olaf.dietsche#list.linux-kernel@t-online.de>:
> I just downloaded glibc 2.3.1 and would say you can
subvert a
> privileged executable with LD_PRELOAD. There's no
mention of
> PR_GET_DUMPABLE anywhere and __libc_enable_secure is
set according to
> some euid/egid tests.
In theory you should be able to just replace the
__libc_enable_secure check with
__libc_enable_secure = !prctl(PR_GET_DUMPABLE);
i.e. let the kernel handle the logic of whether a
process is running privileged.If we duplicate it
between kernel and libc, we'll get security bugs.
Cheers
Chris
next prev parent reply other threads:[~2002-10-29 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:07 [PATCH][RFC] 2.5.42 " Olaf Dietsche
2002-10-18 23:00 ` Alexander Viro
2002-10-19 0:07 ` Olaf Dietsche
2002-10-19 0:25 ` Alexander Viro
2002-10-24 12:25 ` [PATCH][RFC] 2.5.44 " Olaf Dietsche
2002-10-28 22:56 ` Olaf Dietsche
2002-10-28 23:36 ` chris
2002-10-29 0:20 ` Olaf Dietsche
2002-10-29 1:08 ` Olaf Dietsche
2002-10-29 11:08 ` Olaf Dietsche
2002-10-29 11:18 ` Chris Evans [this message]
2002-10-29 2:23 ` Andreas Gruenbacher
2002-10-29 11:09 ` Olaf Dietsche
2002-10-29 11:35 ` Andreas Gruenbacher
2002-10-29 12:04 ` __libc_enable_secure check (was: [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch) Olaf Dietsche
2002-10-29 14:38 ` [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch Olaf Dietsche
2002-10-20 0:24 ` [PATCH][RFC] 2.5.42 " Andreas Gruenbacher
2002-10-21 15:25 ` Olaf Dietsche
2002-10-21 22:03 ` Andreas Gruenbacher
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=E186UO6-0000sD-00@sphinx.mythic-beasts.com \
--to=chris@scary.beasts.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
/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
all inboxes | Powered by JetHome®