From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, lwn@lwn.net,
fedora-selinux-list@redhat.com, selinux@tycho.nsa.gov,
ubuntu-hardened@lists.ubuntu.com,
Linux Security Summit Program Committee
<lss-pc@lists.linuxfoundation.org>,
netfilter-devel@vger.kernel.org, linux-crypto@vger.kernel.org,
Audit-ML <linux-audit@redhat.com>,
gentoo-hardened@gentoo.org, keyrings@linux-nfs.org,
tpmdd-devel@lists.sourceforge.net,
kernel-hardening@lists.openwall.com,
oss-security@lists.openwall.com
Subject: [ANNOUNCE] Linux Security Summit 2016 - CFP
Date: Fri, 25 Mar 2016 09:55:41 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1603250947150.31257@namei.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
==========================================================================
ANNOUNCEMENT AND CALL FOR PARTICIPATION
LINUX SECURITY SUMMIT 2016
25-26 AUGUST
TORONTO, CANADA
==========================================================================
DESCRIPTION
The Linux Security Summit (LSS) is a technical forum for collaboration
between Linux developers, researchers, and end users. Its primary aim
is to foster community efforts in analyzing and solving Linux security
challenges.
The format of the summit will be:
* Refereed presentations
* Discussion topics
* Subsystem reports
* Breakout development sessions
WEB SITE
http://events.linuxfoundation.org/events/linux-security-summit
TWITTER
For event updates and announcements, follow:
https://twitter.com/LinuxSecSummit
DATES / LOCATION
The Linux Security Summit for 2016 will be held August 25th and 26th
in Toronto, Canada. It will be co-located with LinuxCon.
The Linux Security Summit CFP is now open, and will close on June 10th.
Accepted speakers will be notified by June 17th.
WHO SHOULD ATTEND
We're seeking a diverse range of attendees, and welcome participation
by people involved in Linux security development, operations, and research.
The LSS is a unique global event which provides the opportunity to present
and discuss your work or research with key Linux security community
members and maintainers. It’s also useful for those who wish to keep up
with the latest in Linux security development, and to provide input to
the development process.
CALL FOR PARTICIPATION
The program committee currently seeks proposals for:
* Refereed Presentations:
45 minutes in length, including at least 10 minutes of discussion.
One-page abstracts are encouraged.
* Discussion Topics:
30 minutes in length.
Topic areas include, but are not limited to:
* Kernel self-protection
* Access control
* Cryptography and key management
* Integrity control
* Hardware security
* Trust systems
* Storage and file systems
* Virtualization and containers
* Case studies
* Identity management
* Code analysis
* Security analytics
* Secure development and operational practices
* Emerging technologies, threats & techniques
Proposals should be submitted via the event web site:
http://events.linuxfoundation.org/events/linux-security-summit/program/cfp
PROGRAM COMMITTEE
The Linux Security Summit for 2016 is organized by:
* James Morris, Oracle
* Serge Hallyn, Canonical
* Paul Moore, Red Hat
* Stephen Smalley, NSA
* Elena Reshetova, Intel
* Herbert Xu, Red Hat
* John Johansen, Canonical
* Kees Cook, Google
* Casey Schaufler, Intel
* Mimi Zohar, IBM
The program committee may be contacted as a group via email:
lss-pc@lists.linuxfoundation.org
reply other threads:[~2016-03-24 22:55 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=alpine.LRH.2.20.1603250947150.31257@namei.org \
--to=jmorris@namei.org \
--cc=fedora-selinux-list@redhat.com \
--cc=gentoo-hardened@gentoo.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-audit@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lss-pc@lists.linuxfoundation.org \
--cc=lwn@lwn.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=oss-security@lists.openwall.com \
--cc=selinux@tycho.nsa.gov \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=ubuntu-hardened@lists.ubuntu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox