From: Crispin Cowan <crispin@novell.com>
To: linux-security-module@vger.kernel.org,
apparmor-dev <apparmor-dev@forge.novell.com>,
SELinux ML <selinux@tycho.nsa.gov>,
Bastille Linux Announce
<bastille-linux-announce@lists.bastille-linux.org>,
apparmor-announce@forge.novell.com,
AppArmor Mailinglist <apparmor-general@forge.novell.com>
Subject: Security BoF at LinuxWorld
Date: Fri, 20 Jul 2007 19:28:12 -0700 [thread overview]
Message-ID: <46A16F3C.3080307@novell.com> (raw)
For those attending LinuxWorld <http://www.linuxworldexpo.com/live/12/>
next month in San Francisco, there will be a BoF on Linux Intrusion
Prevention and Security
<http://www.linuxworldexpo.com/live/12/events/12SFO07A/conference/tracksessions//QMONYB001HXO>.
LSM is one of the primary ways to implement security and intrusion
prevention enhancements, people on this list might be interested.
There are already separate sessions on SELinux
<http://www.linuxworldexpo.com/live/12/events/12SFO07A/conference/tracksessions/Security/QMONYB00129X>,
AppArmor
<http://www.linuxworldexpo.com/live/12/events/12SFO07A/conference/tracksessions/Security/QMONYB00129R>,
and Bastille
<http://www.linuxworldexpo.com/live/12/events/12SFO07A/conference/tracksessions/Security/QMONYB0012A4>
so while these systems are likely to come up, I would hope that we spend
most of the time talking about other projects, or more general topics
such as how to improve the LSM interface.
Crispin
--
Crispin Cowan, Ph.D. http://crispincowan.com/~crispin/
Director of Software Engineering http://novell.com
AppArmor Chat: irc.oftc.net/#apparmor
--
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.
reply other threads:[~2007-07-23 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46A16F3C.3080307@novell.com \
--to=crispin@novell.com \
--cc=apparmor-announce@forge.novell.com \
--cc=apparmor-dev@forge.novell.com \
--cc=apparmor-general@forge.novell.com \
--cc=bastille-linux-announce@lists.bastille-linux.org \
--cc=linux-security-module@vger.kernel.org \
--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.