Keyrings 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>,
	 linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com,
	 linux-integrity@vger.kernel.org, lwn@lwn.net,
	linux-crypto@vger.kernel.org,  keyrings@vger.kernel.org
Subject: [ANN] Linux Security Summit 2026 CfP
Date: Mon, 26 Jan 2026 12:58:17 -0800 (PST)	[thread overview]
Message-ID: <4c3e8881-fc8d-a413-d3d1-be2a295de13@namei.org> (raw)

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

                   LINUX SECURITY SUMMIT NORTH AMERICA 2026
                             
                                  May 21-22
                             Minneapolis, MN, USA
==============================================================================

DESCRIPTION
 
Linux Security Summit North America (LSS-NA) 2026 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.

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

SUGGESTED TOPICS

    * 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

DATES TO REMEMBER:

    * CFP Close: Sunday, March 15 at 11:59 PM CDT
    * CFP Notifications: Tuesday, March 31
    * Schedule Announced: Thursday, April 2
    * Event Date: Thursday, May 21 - Friday, May 22

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.

MASTODON

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

PROGRAM COMMITTEE

  The program committee for LSS 2026 is:

    * James Morris, Microsoft
    * Serge Hallyn, Geico
    * 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:[~2026-01-26 21:03 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=4c3e8881-fc8d-a413-d3d1-be2a295de13@namei.org \
    --to=jmorris@namei.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=keyrings@vger.kernel.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).