problems after selinux-policy-targeted-1.17.30-3.2 update

[varol kaptan]

Hi,

I have a shared library that I create and use within my application.
After the update the thing stopped working. Here is some information:

ls -Z /usr/bin/lua
-rwxr-xr-x  root     root     system_u:object_r:bin_t          /usr/bin/lua
ls -Z /home/varol/src/lua/lib/memarray.so
-rwxrwxr-x  varol    varol    user_u:object_r:user_home_t     
/home/varol/src/lua/lib/memarray.so

tail -f /var/log/messages
Jun 13 12:03:45 thales kernel: audit(1118660625.243:0): avc:  denied 
{ execmod } for  pid=3021 comm=lua
path=/home/varol/src/lua/lib/memarray.so dev=dm-1 ino=753702
scontext=user_u:system_r:unconfined_t
tcontext=user_u:object_r:user_home_t tclass=file

I had other problems too (acrobat 7) but was able to fix them by going
through the mailing lists.

My question is: How do I fix the above problem, and is there a way to
fix the mess introduced with the latest
selinux-policy-targeted-1.17.30-3.2 update once and for all?

Thanks in advance,
Varol Kaptan

[Daniel J Walsh]

varol kaptan wrote:

> Hi,
>
> I have a shared library that I create and use within my application.
> After the update the thing stopped working. Here is some information:
>
> ls -Z /usr/bin/lua
> -rwxr-xr-x  root     root     system_u:object_r:bin_t          /usr/bin/lua
> ls -Z /home/varol/src/lua/lib/memarray.so
> -rwxrwxr-x  varol    varol    user_u:object_r:user_home_t     
> /home/varol/src/lua/lib/memarray.so
>
> tail -f /var/log/messages
> Jun 13 12:03:45 thales kernel: audit(1118660625.243:0): avc:  denied 
> { execmod } for  pid=3021 comm=lua
> path=/home/varol/src/lua/lib/memarray.so dev=dm-1 ino=753702
> scontext=user_u:system_r:unconfined_t
> tcontext=user_u:object_r:user_home_t tclass=file
>
> I had other problems too (acrobat 7) but was able to fix them by going
> through the mailing lists.
>
> My question is: How do I fix the above problem, and is there a way to
> fix the mess introduced with the latest
> selinux-policy-targeted-1.17.30-3.2 update once and for all?
>
> Thanks in advance,
> Varol Kaptan
>
> --
> fedora-selinux-list mailing list
> fedora-selinux-list(a)redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-selinux-list
>   
>  
setsebool -P allow_execmod=1

--

[varol kaptan]

On 6/13/05, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
>  varol kaptan wrote:
>  
>  >Hi,
>  >
>  >I have a shared library that I create and use within my application.
>  >After the update the thing stopped working. Here is some information:
>  >
>  >ls -Z /usr/bin/lua
>  >-rwxr-xr-x  root     root     system_u:object_r:bin_t          /usr/bin/lua
>  >ls -Z /home/varol/src/lua/lib/memarray.so
>  >-rwxrwxr-x  varol    varol    user_u:object_r:user_home_t
>  >/home/varol/src/lua/lib/memarray.so
>  >
>  >tail -f /var/log/messages
>  >Jun 13 12:03:45 thales kernel: audit(1118660625.243:0): avc:  denied
>  >{ execmod } for  pid=3021 comm=lua
>  >path=/home/varol/src/lua/lib/memarray.so dev=dm-1 ino=753702
>  >scontext=user_u:system_r:unconfined_t
>  >tcontext=user_u:object_r:user_home_t tclass=file
>  >
>  >I had other problems too (acrobat 7) but was able to fix them by going
>  >through the mailing lists.
>  >
>  >My question is: How do I fix the above problem, and is there a way to
>  >fix the mess introduced with the latest
>  >selinux-policy-targeted-1.17.30-3.2 update once and for all?
>  >
>  >Thanks in advance,
>  >Varol Kaptan
>  >
>  >--
>  >fedora-selinux-list mailing list
>  &gt;fedora-selinux-list(a)redhat.com
>  >http://www.redhat.com/mailman/listinfo/fedora-selinux-list
>  >
>  >
>  setsebool -P allow_execmod=1 
Nope, does not work.

Thanks,
Varol Kaptan