|
Message-ID: <alpine.LRH.2.21.1904100829230.16313@namei.org> Date: Wed, 10 Apr 2019 08:34:51 +1000 (AEST) From: James Morris <jmorris@...ei.org> To: linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org cc: lwn@....net, fedora-selinux-list@...hat.com, Linux Security Summit Program Committee <lss-pc@...ts.linuxfoundation.org>, linux-crypto@...r.kernel.org, Audit-ML <linux-audit@...hat.com>, gentoo-hardened@...too.org, keyrings@...ux-nfs.org, tpmdd-devel@...ts.sourceforge.net, kernel-hardening@...ts.openwall.com, linux-integrity@...r.kernel.org, selinux@...r.kernel.org Subject: [ANNOUNCE][CFP] Linux Security Summit North America 2019 ============================================================================== ANNOUNCEMENT AND CALL FOR PARTICIPATION LINUX SECURITY SUMMIT NORTH AMERICA 2019 19-21 August SAN DIEGO, CA, USA ============================================================================== 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. * Tutorials (NEW for 2019) 90 minutes in length. * Hackfest Sessions (NEW for 2019) 1/2 day. Note that LSS NA is now a 3-day event. The third day will be a mix of tutorials and hackfest sessions: * 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. * Hackfest proposals should aim to solve, or make significant progress on a well-defined problem in the Linux security defense space, and be supported by multiple community developers. Topic areas include, but are not limited to: * Kernel self-protection * Access control * Cryptography and key management * Integrity policy and enforcement * 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-2019/program/cfp/ DATES * CFP Close: May 31, 2019 * CFP Notifications: June 17, 2019 * Schedule Announced: June 19, 2019 * Event: August 19-21, 2019 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-2019/ TWITTER For event updates and announcements, follow: https://twitter.com/LinuxSecSummit PROGRAM COMMITTEE The program committee for LSS 2019 is: * James Morris, Microsoft * Serge Hallyn, Cisco * Paul Moore, Cisco * 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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.