Subject: | |
From: | |
Reply To: | |
Date: | Tue, 19 Jun 2007 19:52:28 +0100 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
On Tue, 19 Jun 2007, [log in to unmask] wrote:
> On Mon, 18 Jun 2007, Michael Hannon wrote:
>
> [...]
>> > > ImportError:
>> > > /usr/lib/python2.4/site-packages/rdiff_backup/_librsync.so:
>> > > cannot restore segment prot after reloc: Permission denied
> [...]
>> correct: setting selinux to "Permissive" mode makes the error go away.
>
> Instead of effectively disabling SELinux (in permissive mode, you still get
> the annoying messages but not any protection ;-), relabelling the library
> would probably work as well:
>
> chcon -t texrel_shlib_t .../_librsync.so
Very few things seem to have that context by default. Certainly none of
the libs in /lib seem to...
$ ls -ldZ /lib/lib*.so| grep shlib_t | wc -l
0
is this a flaw in my installation or are those .so files treated
differently for some reason? Or do those simply not need it?
If that should be the right context should the package (or restorecon?)
set that automatically?
How should one make this kind of thing work for (e.g.) user-installed
python modules over NFS (ie without context support) or other things which
need similar magic?
-- Jon
|
|
|