public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Location of hard coded IA32 libraries
Date: Mon, 10 Sep 2001 09:26:08 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805150@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805123@msgid-missing>

>>>>> "Don" = Don Dugger <n0ano@valinux.com> writes:

Don> That's a pretty stong argument for not using the environment
Don> variable approach.  If we go with using a hard coded path, like
Don> `/usr/ia32', then there is no security hole.  This just becomes
Don> another tree that has to have protected files the same way `/'
Don> needs protected files.

I don't see the problem for environment variables either, LD_IA32_PATH
should just be treated like LD_LIBRARY_PATH and do magic for suid
binaries. On the other hand if the sysadmin allows you to overwrite
/usr/ia32/lib then you are in the same situation as if the user can
overwrite /usr/lib ;-)

Cheers
Jes


      reply	other threads:[~2001-09-10  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 17:28 [Linux-ia64] Location of hard coded IA32 libraries Don Dugger
2001-09-10  9:26 ` Jes Sorensen [this message]

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=marc-linux-ia64-105590698805150@msgid-missing \
    --to=jes@sunsite.dk \
    --cc=linux-ia64@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