From: ramsdell@mitre.org (John D. Ramsdell)
To: selinux@tycho.nsa.gov
Subject: Cannot run ldconfig in a home directory
Date: 17 Jul 2007 07:39:30 -0400 [thread overview]
Message-ID: <ogtzm1vntsd.fsf@oolong.mitre.org> (raw)
I am playing around with the source distribution of the audit package.
I modified some code, but I don't want to install the modified version
in the usual locations, just in case I break something. So I
configured the source distribution using:
$ ./configure --prefix=$HOME/opt/audit
and then did the usual "make; make install".
The audit package contains shared libraries, and the installation
scripts run ldconfig using the -n option. This option ensures
ldconfig will not process the trusted directories (/usr/lib and /lib)
or those specified in /etc/ld.so.conf, thus allowing it to be run
by an unprivileged user; however, the current SELinux for Fedora 7
prevents this usage of ldconfig. Setroubleshoot reports:
Summary:
SELinux is preventing /sbin/ldconfig (ldconfig_t) "search" to home
(home_root_t).
Detailed Description:
SELinux denied access requested by /sbin/ldconfig. It is not expected
that this access is required by /sbin/ldconfig and this access may
signal an intrusion attempt. It is also possible that the specific
version or configuration of the application is causing it to require
additional access.
Obviously, it is easy enough for me to disable SELinux while playing
with the audit sources, but it seems to that with this policy, if I
were working on a machine I did not control, I wouldn't be able
properly test an installation.
John
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2007-07-17 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 11:39 John D. Ramsdell [this message]
2007-07-17 12:03 ` Cannot run ldconfig in a home directory Michal Piotrowski
2007-07-17 12:14 ` John D. Ramsdell
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=ogtzm1vntsd.fsf@oolong.mitre.org \
--to=ramsdell@mitre.org \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.