John Bussoletti wrote:
Sage Dev Staff:
The command "sestatus" returns the following text on my system:
SELinux Status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: permissive
Policy version: 24
Policy from config file: targeted
So it seems that if you grep for "Current mode" and find either "disabled"
or "permissive", sage should build, but if you encounter "enabled" then it
may fail to build those apps that make the stack executable.
On my system sestatus is in /usr/sbin.
John Bussoletti
A better method would be to write a program which attempts to execute something
on the stack and see if that fails or not. The advantage of that is that it
would work on any system which has stack protection. (Solaris has it, though it
is not enabled on 32-bit code by default, though I think it is for 64-bit.)
With time, I can see stack protection being more common, so determine if its
operating on many different systems might be a bit of a pain, whereas a test
would only need to be written once.
Better still, is fix the software that is trying to execute the stack!
I don't personally know how to write a program that executes the stack, but I
doubt it is hard to find information on how to do it.
Dave
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
To unsubscribe from this group, send email to sage-support+unsubscribegooglegroups.com or
reply to this email with the words "REMOVE ME" as the subject.
