Incidentally, another SELinux hit on my plate is allow_execstack. If
this boolean is not enabled, then libdyninstAPI_RT.so is completely
blocked. Now, it's obvious why Dyninst needs to both write and execute
the same memory, but the default security settings are understandably
wary of such games. See:
http://www.akkadia.org/drepper/selinux-mem.html
I'm not certain why Dyninst is triggering execstack rather than execmem,
but anyway...
To avoid these protections, it suggests mapping the same memory at two
locations, once writable and once executable. So this is another thing
I might look into doing for Dyninst, if you're game.
I believe that Dyninst is anathema to SELinux. But hey...
Again, that would be appreciated.
Drew
-- Andrew Bernat Paradyn Project
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}