From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, lwn@lwn.net,
fedora-selinux-list@redhat.com, linux-crypto@vger.kernel.org,
kernel-hardening@lists.openwall.com,
linux-integrity@vger.kernel.org, selinux@vger.kernel.org,
Audit-ML <linux-audit@redhat.com>,
gentoo-hardened@gentoo.org, keyrings@linux-nfs.org,
tpmdd-devel@lists.sourceforge.net,
Linux Security Summit Program Committee
<lss-pc@lists.linuxfoundation.org>
Subject: Re: [ANNOUNCE][CFP] Linux Security Summit 2021
Date: Tue, 22 Jun 2021 12:46:43 +1000 (AEST) [thread overview]
Message-ID: <2db579ee-1d1c-102c-c2d4-c268d89aae8c@namei.org> (raw)
In-Reply-To: <5b3a0bf-226d-6ee-d0b-d6673eff32b2@namei.org>
Two further (and hopefully final) changes:
- LSS 2021 will now be a hybrid event, catering to both in-person and
remote attendees and presenters
- The CFP is extended to July 11th.
On Wed, 26 May 2021, James Morris wrote:
> Note that the venue of LSS 2021 has now changed to Seattle, USA.
>
> See https://events.linuxfoundation.org/linux-security-summit-north-america/
>
> The new event dates are 29 September to 01 October.
>
> The CFP closes on June 27th.
>
>
>
>
>
> On Tue, 9 Feb 2021, James Morris wrote:
>
> > ==============================================================================
> > ANNOUNCEMENT AND CALL FOR PARTICIPATION
> >
> > LINUX SECURITY SUMMIT 2021
> >
> > 27-29 September
> > Dublin, Ireland
> > ==============================================================================
> >
> > DESCRIPTION
> >
> > 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.
> >
> > 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 a leading subject matter expert on the topic.
> >
> > 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/linux-security-summit-europe/program/cfp/
> >
> >
> > ** Note that for 2021, the North American and European events are combined into
> > a single event planned for Dublin, Ireland. **
> >
> >
> > DATES
> >
> > * CFP close: June 27
> > * CFP notifications: July 20
> > * Schedule announced: July 22
> > * Event: September 27-29
> >
> > 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-europe/
> >
> > TWITTER
> >
> > For event updates and announcements, follow:
> >
> > https://twitter.com/LinuxSecSummit
> >
> > #linuxsecuritysummit
> >
> > PROGRAM COMMITTEE
> >
> > The program committee for LSS 2021 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
> >
> >
>
> --
> James Morris
> <jmorris@namei.org>
>
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2021-06-22 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 19:59 [ANNOUNCE][CFP] Linux Security Summit 2021 James Morris
2021-05-25 16:24 ` James Morris
2021-06-22 2:46 ` James Morris [this message]
2021-09-14 2:44 ` James Morris
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=2db579ee-1d1c-102c-c2d4-c268d89aae8c@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-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 \
--cc=selinux@vger.kernel.org \
--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).