tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: lwn@lwn.net, fedora-selinux-list@redhat.com,
	selinux@tycho.nsa.gov,
	Linux Security Summit Program Committee
	<lss-pc@lists.linuxfoundation.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
Subject: [ANNOUNCE] Linux Security Summit North America 2018 - CFP
Date: Tue, 10 Apr 2018 09:14:19 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1804100911160.11121@namei.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]

==============================================================================
		   ANNOUNCEMENT AND CALL FOR PARTICIPATION

		   LINUX SECURITY SUMMIT NORTH AMERICA 2018
                             
			         27-28 August
			       VANCOUVER, 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.

  LSS will be held this year as two separate events, one in North America
  (LSS-NA), and one in Europe (LSS-EU), to facilitate broader participation in
  Linux Security development. Note that this CFP is for LSS-NA; a separate CFP
  will be announced for LSS-EU in May. We encourage everyone to attend both
  events.

  The program committee currently seeks proposals for:

    * Refereed Presentations:
      45 minutes in length.

    * Panel Discussion Topics:
      45 minutes in length.

    * Short Topics:
      30 minutes in total, including at least 10 minutes discussion.

    * BoF Sessions.

  Topic areas include, but are not limited to:

    * Kernel self-protection
    * Access control
    * Cryptography and key management
    * Integrity control
    * Hardware Security
    * Iot and embedded security
    * Virtualization and containers
    * System-specific system hardening
    * Case studies
    * Security tools
    * Security UX
    * Emerging technologies, threats & techniques 

  Proposals should be submitted via:
    https://events.linuxfoundation.org/events/linux-security-summit-north-america-2018/program/cfp/


DATES

  * CFP Close: June 3, 2018
  * CFP Notifications: June 11, 2018
  * Schedule Announced: June 25, 2018
  * Event: August 27-28, 2018


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.


WEB SITE

  https://events.linuxfoundation.org/events/linux-security-summit-north-america-2018/


TWITTER

  For event updates and announcements, follow:

    https://twitter.com/LinuxSecSummit
  

PROGRAM COMMITTEE

  The program committee for LSS 2018 is:

    * James Morris, Microsoft
    * Serge Hallyn, Cisco
    * Paul Moore, Red Hat
    * Stephen Smalley, NSA
    * Elena Reshetova, Intel
    * John Johansen, Canonical
    * Kees Cook, Google
    * Casey Schaufler, Intel
    * Mimi Zohar, IBM
    * David A. Wheeler, Institute for Defense Analyses

  The program committee may be contacted as a group via email:
    lss-pc () lists.linuxfoundation.org

                 reply	other threads:[~2018-04-09 23:14 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.21.1804100911160.11121@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=selinux@tycho.nsa.gov \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).