From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Make LD_ASSUME_KERNEL working even for static binaries
Date: Mon, 09 Dec 2002 13:43:00 -0000 [thread overview]
Message-ID: <3DF50E9D.5020806@redhat.com> (raw)
In-Reply-To: <20021209162539.J27455@devserv.devel.redhat.com>
Jakub Jelinek wrote:
> I'm not sure either way. LD_ASSUME_KERNEL in ld.so ATM is not limited to
> non-suid.
I don't think it is necessary to use __secure_getenv. It doesn't let
the user directly make decisions about what DSO is used. And if the
DSOs with support are vulnerable to something the new DSOs are not there
are other ways to get to this.
--
--------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
next prev parent reply other threads:[~2002-12-09 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 10:29 Jakub Jelinek
2002-12-09 12:50 ` Roland McGrath
[not found] ` <20021209162539.J27455@devserv.devel.redhat.com>
2002-12-09 13:43 ` Ulrich Drepper [this message]
2002-12-09 13:45 ` Roland McGrath
2002-12-10 2:31 ` Roland McGrath
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=3DF50E9D.5020806@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).