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
Subject: [Announce] Linux Security Summit North America 2025 CfP
Date: Mon, 10 Feb 2025 13:03:02 -0800 (PST) [thread overview]
Message-ID: <35b17495-427f-549f-6e46-619c56545b34@namei.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
The Call for Participation for the 2025 Linux Security Summit North
America (LSS-NA) is now open.
LSS-NA 2025 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.
Key dates:
- CFP Closes: Monday, March 10 at 11:59 PM MDT / 10:59 PM PDT
- CFP Notifications: Monday, March 31
- Schedule Announcement: Wednesday, April 2
- Presentation Slide Due Date: Tuesday, June 24
- Event Dates: Thursday, June 26 – Friday, June 27
Location: Denver, Colorado, USA (co-located with OSS).
Full details may be found here:
https://events.linuxfoundation.org/linux-security-summit-north-america/
Follow LSS event updates here:
https://social.kernel.org/LinuxSecSummit
--
James Morris
<jmorris@namei.org>
next reply other threads:[~2025-02-10 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 21:03 James Morris [this message]
2025-02-17 12:45 ` [Announce] Linux Security Summit North America 2025 CfP Dr. Greg
2025-02-17 15:45 ` Casey Schaufler
2025-02-19 6:44 ` [Announce] Linux Security Summit Europe " Reshetova, Elena
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=35b17495-427f-549f-6e46-619c56545b34@namei.org \
--to=jmorris@namei.org \
--cc=kernel-hardening@lists.openwall.com \
--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