From: "Patrick K., ITF" <cto@itechfrontiers.com>
To: Andrew Holway <andrew.holway@otternetworks.de>, selinux@tycho.nsa.gov
Subject: Re: SELinux talk
Date: Tue, 12 May 2015 11:29:09 -0400 [thread overview]
Message-ID: <55521C45.1010105@itechfrontiers.com> (raw)
In-Reply-To: <CAEcA1_vvm7TEkrULWOxbC=BtuCyn+Tm0DMXLE3ScZe24Lktpjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Andrew,
Please visit:
http://www.tresys.com/innovation/library.php
Best Regards,
--
Patrick K.
On 5/12/2015 10:42 AM, Andrew Holway wrote:
> Hello,
>
> I'm giving a talk on SELinux at a little conference here in Berlin in
> a couple of days. I was going to do the following items.
>
> IEEE 1003.1e/2c - A withdrawn draft standard.
> Linux ACLS - Hacked together from IEEE 1003.1e/2c
> SELinux -> An opensource solution for the US military.
> DAC 1997 -> 2015 - The elephant in the room.
>
> I was wondering if anyone could provide me with specific bulletpoint
> examples of the problems inherent with the current ACL system and how
> SELinux can mitigate these problems.
>
> Can anyone tell me about the relationship between IEEE 1003.1e/2c and
> SELinux?
>
> Any other interesting nuggets to keep a technical but non security
> focussed audience interested?
>
> Ta
>
> Andrew
>
>
>
> --
> Otter Networks UG
> http://otternetworks.de
> fon: +49 30 54 88 5197
> Gotenstraße 17
> 10829 Berlin
>
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov.
[-- Attachment #2: Type: text/html, Size: 3101 bytes --]
next prev parent reply other threads:[~2015-05-12 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 14:42 SELinux talk Andrew Holway
2015-05-12 15:12 ` Dominick Grift
2015-05-12 16:00 ` Dominick Grift
2015-05-12 15:29 ` Patrick K., ITF [this message]
2015-05-12 16:57 ` Stephen Smalley
2015-05-13 2:09 ` Casey Schaufler
-- strict thread matches above, loose matches on Subject: below --
2004-10-02 22:16 Colin Walters
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=55521C45.1010105@itechfrontiers.com \
--to=cto@itechfrontiers.com \
--cc=andrew.holway@otternetworks.de \
--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.