| 1 |
Am Dienstag, 25.10.2016 um 20:23 |
| 2 |
schrieb "PaX Team" <pageexec@××××××××.hu>: |
| 3 |
|
| 4 |
> On 25 Oct 2016 at 19:35, wabe wrote: |
| 5 |
> |
| 6 |
> > Interesting. I'm using hardened-sources-4.7.6 and qemu-2.7.0-r4 and |
| 7 |
> > don't have any problems so far. I'm using qemu VMs with xubuntu |
| 8 |
> > 14.04 and 16.04. |
| 9 |
> |
| 10 |
> do you enable SANITIZE? 'cos that's what seems to trigger the problem |
| 11 |
> for Miroslav. |
| 12 |
|
| 13 |
I don't have this feature enabled because of a possible performance |
| 14 |
impact. My system is already slow enough. ;-) |
| 15 |
|
| 16 |
Symbol: PAX_MEMORY_SANITIZE [=n] |
| 17 |
Type : boolean |
| 18 |
Prompt: Sanitize all freed memory |
| 19 |
Location: |
| 20 |
-> Security options |
| 21 |
-> Grsecurity |
| 22 |
-> Grsecurity (GRKERNSEC [=y]) |
| 23 |
-> Customize Configuration |
| 24 |
-> PaX |
| 25 |
-> Miscellaneous hardening features |
| 26 |
|
| 27 |
-- |
| 28 |
Regards |
| 29 |
wabe |
Archives