| 1 |
On 3 May 2007 at 14:47, Miguel Sousa Filipe wrote: |
| 2 |
|
| 3 |
> In LISP, data and code are one and the same, so all hardened profiles |
| 4 |
> believe that any LISP environment is "violating" simple principles |
| 5 |
> such has"executing data". |
| 6 |
> |
| 7 |
> Having heap and stack without execution permissions invalidate the use |
| 8 |
> of LISP .. since it needs do execute data. |
| 9 |
> |
| 10 |
> I've don't recall being able to use lisp on setups where the process |
| 11 |
> heap is not executable. But I could be proven wrong... |
| 12 |
|
| 13 |
runtime code generation is very well possible under hardened setups, |
| 14 |
it's just that it must be enabled explicitly for the apps that need |
| 15 |
it, it's no longer granted by default. on gentoo/PaX setups you'd |
| 16 |
use paxctl -m which is normally done by the ebuild, see e.g., java. |
| 17 |
|
| 18 |
however there're programs which need this exemption during build |
| 19 |
already - that case requires more work to handle as we have to |
| 20 |
figure out where and how to patch the build system of the given |
| 21 |
package. there're also issues with text relocations, some of which |
| 22 |
require serious programming work to fix (see e.g., bug 134403). |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-hardened@g.o mailing list |
Archives