From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Cc: Linux Security Summit Program Committee
<lss-pc@lists.linuxfoundation.org>,
keyrings@linux-nfs.org, gentoo-hardened@gentoo.org,
kernel-hardening@lists.openwall.com, selinux@vger.kernel.org,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
Audit-ML <linux-audit@redhat.com>,
linux-crypto@vger.kernel.org, lwn@lwn.net,
linux-integrity@vger.kernel.org
Subject: [tpmdd-devel] [ANNOUNCE] Linux Security Summit North Americ (LSS-NA) CfP
Date: Sat, 21 Jan 2023 09:24:57 +1100 (AEDT) [thread overview]
Message-ID: <3a8f10eb-df2-cfad-1d-5aeab14568e@namei.org> (raw)
The Call for Participation for the 2023 LSS-NA conference is open!
See details of the event and information on submitting proposals here:
https://events.linuxfoundation.org/linux-security-summit-north-america/
LSS-NA 2023 will be in Vancouver, BC, Canada, from May 10th to May 12th.
This will be a three day event, co-located with Open Source Summit North
America [1].
The LSS-NA CfP is open until March 1st, 2023.
Note that announcements relating to the Linux Security Summit may be found
now on the Fediverse, via: https://social.kernel.org/LinuxSecSummit
--
James Morris
<jmorris@namei.org>
[1] https://events.linuxfoundation.org/open-source-summit-north-america/
_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
reply other threads:[~2023-01-20 23:08 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=3a8f10eb-df2-cfad-1d-5aeab14568e@namei.org \
--to=jmorris@namei.org \
--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).