kernel-hardening.lists.openwall.com archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Cc: Linux Security Summit Program Committee
	<lss-pc@lists.linuxfoundation.org>,
	 lwn@lwn.net, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org,
	 kernel-hardening@lists.openwall.com,
	linux-integrity@vger.kernel.org,
	 Audit-ML <linux-audit@redhat.com>
Subject: [ANNOUNCE] CFP: Linux Security Summit North America 2024
Date: Wed, 29 Nov 2023 13:19:31 -0800 (PST)	[thread overview]
Message-ID: <826fd432-1acf-16be-e7a9-d692aeed23f0@namei.org> (raw)


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

                   LINUX SECURITY SUMMIT NORTH AMERICA 2024
                             
                                 April 18-19
                              Seattle, WA, USA
==============================================================================

DESCRIPTION
 
Linux Security Summit North America 2024 is a technical forum for
collaboration between Linux developers, researchers, and end-users.  Its
primary aim is to foster community efforts in deeply analyzing and solving
Linux operating system security challenges, including those in the Linux
kernel.

Presentations are expected to focus deeply on new or improved technology and
how it advances the state of practice for addressing these challenges.

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.
 
   * Tutorials
     90 minutes in length.

Tutorial sessions should be focused on advanced Linux security defense
topics within areas such as the kernel, compiler, and security-related
libraries.  Priority will be given to tutorials created for this conference,
and those where the presenter is a leading subject matter expert on the
topic.
 
Topic areas include, but are not limited to:

    * Access Control
    * Case Studies
    * Cryptography and Key Management
    * Emerging Technologies, Threats & Techniques
    * Hardware Security
    * IoT and Embedded Security
    * Integrity Policy and Enforcement
    * Open Source Supply Chain for the Linux OS
    * Security Tools
    * Security UX
    * Linux OS Hardening
    * Virtualization and Containers

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


LSS-NA DATES
 
  * CFP close:            Jan 21, 2024
  * CFP notifications:    Feb 06, 2024
  * Schedule announced:   Feb 08, 2024
  * Event:                Apr 18-19, 2024


WHO SHOULD ATTEND
 
We're seeking a diverse range of attendees and welcome participation by
people involved in Linux security development, operations, and research.
 
LSS is a unique global event that 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/linux-security-summit-north-america/


MASTODON

  For event updates and announcements, follow:
    
    https://social.kernel.org/LinuxSecSummit
  
  #linuxsecuritysummit


PROGRAM COMMITTEE

  The program committee for LSS 2024 is:

    * James Morris, Microsoft
    * Serge Hallyn, Cisco
    * Paul Moore, Microsoft
    * Stephen Smalley, NSA
    * Elena Reshetova, Intel
    * John Johansen, Canonical
    * Kees Cook, Google
    * Casey Schaufler
    * Mimi Zohar, IBM
    * David A. Wheeler, Linux Foundation

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


                 reply	other threads:[~2023-11-29 21:19 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=826fd432-1acf-16be-e7a9-d692aeed23f0@namei.org \
    --to=jmorris@namei.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@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 \
    /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).