tracking down execstack & execmem violations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm writing a policy for a very large legacy CORBA application, with
many separate processes. Without fail, every one of our processes
requires execstack & execmem privileges. I would like to track down the
cause, but I really don't have any idea how. Does anybody have any good
recommendations?

I'd like to at least be able to determine whether the offending code is
ours or some vender's (like our CORBA vender), and if it is ours I'd
like to track down the source. I'm betting there is a common source
causing the issue.

Thanks







--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux