All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Nikolay <Nikolay@alexandrov.ws>
Cc: selinux@tycho.nsa.gov
Subject: Re: Some ideas and info.
Date: Sun, 1 Aug 2004 10:50:06 +0100	[thread overview]
Message-ID: <20040801095006.GA7384@lkcl.net> (raw)
In-Reply-To: <200408010121.i711LUHs013906@mummy.ncsc.mil>

hello nikolay, from one random selinux user to another, welcome to
the nsa's selinux list.

okay.  selinux was designed to add fine grained auditing and "mandatory"
access control because of concerns over the use in US government
departments of an over-20-year-old security model - i.e. ordinary
non-selinux-enhanced linux.

i presume that the nsa's expertise was best spent focussing on this
specific "lack", given that other research projects were concentrating
on things like PAX, MPPE support etc. (e.g. the http://adamantix.org stuff)

so yes, it'd be great to have additional security measures in place.

i think you'll find that gentoo (hardened) have made use of as many
as they can find.

however the people on _this_ list specifically focus on selinux -
perhaps on its own, perhaps in combination with other security measures
(like gentoo hardened do).

so, with that in mind, can i please ask you a favour?

can i "steer" you in the direction of adamantix.org, because i would
_really_ like to see debian have all of the adamantix.org stuff minus
the RSBAC stuff plus selinux stuff.

it's a bit unfortunate that a lot of this stuff requires a total
recompile of all packages, which is probably why gentoo has it a
bit easier.

l.


On Sun, Aug 01, 2004 at 04:20:54AM -0000, 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.

-- 
-- 
Information I post is with honesty, integrity, and the expectation that
you will take full responsibility if acting on the information contained,
and that, should you find it to be flawed or even mildly useful, you
will act with both honesty and integrity in return - and tell me.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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.

      parent reply	other threads:[~2004-08-01  9:39 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
2004-08-01 10:14   ` Luke Kenneth Casson Leighton
2004-08-01  9:50 ` Luke Kenneth Casson Leighton [this message]

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=20040801095006.GA7384@lkcl.net \
    --to=lkcl@lkcl.net \
    --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.