From: Joshua Brindle <jbrindle@tresys.com>
To: Nikolay <nikolay@alexandrov.ws>
Cc: selinux@tycho.nsa.gov
Subject: Re: Some ideas and info.
Date: Sun, 01 Aug 2004 01:46:19 -0400 [thread overview]
Message-ID: <410C83AB.5020305@tresys.com> (raw)
In-Reply-To: <200408010121.i711LUHs013906@mummy.ncsc.mil>
Nikolay wrote:
>Hi. I was wondering if you've thought about implementing non-exec pages and
>stack randomization?
>In case that the user hasn't got the PaX patches it's nice to be protected
>at least a little more isn't it ? I think that at least basic
>implementations of such mechanisms is needed and would help in improving the
>security level.
>I could implement such ideas, if you'd like ofcourse.
>
>(Sorry for my poor english (it's not my native language. I also intend to
>write often here, I like the ideas of your project and I would be glad to
>help you.)
>Best regards,
>Nikolay
>
>
>--
>This message was distributed to subscribers of the selinux mailing list.
>If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
>the words "unsubscribe selinux" without quotes as the message.
>
>
>
Memory protections are well outside the scope of SELinux (which includes
only mandatory access control), however the Gentoo (of which I am a
part) have a patch to integrate PaX flags into SELinux policy, it's
available if you are interested.
Joshua Brindle
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-08-01 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 4:20 Some ideas and info Nikolay
2004-08-01 5:46 ` Joshua Brindle [this message]
2004-08-01 10:14 ` Luke Kenneth Casson Leighton
2004-08-01 9:50 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=410C83AB.5020305@tresys.com \
--to=jbrindle@tresys.com \
--cc=nikolay@alexandrov.ws \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.