From: "Reshetova, Elena" <elena.reshetova@intel.com>
To: "linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>
Cc: "lss-pc@lists.linuxfoundation.org"
<lss-pc@lists.linuxfoundation.org>, "lwn@lwn.net" <lwn@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"selinux@vger.kernel.org" <selinux@vger.kernel.org>,
Audit-ML <linux-audit@redhat.com>,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>
Subject: [ANNOUNCE] [CFP] Linux Security Summit Europe (LSS-EU)
Date: Mon, 17 Apr 2023 08:35:04 +0000 [thread overview]
Message-ID: <DM8PR11MB57509BF8C3350944A3DB0A8FE79C9@DM8PR11MB5750.namprd11.prod.outlook.com> (raw)
The Call for Participation for the 2023 LSS-EU conference is open!
See details of the event and information on submitting proposals here:
https://events.linuxfoundation.org/linux-security-summit-europe/
LSS-EU 2023 will be in Bilbao, Spain, from September 20th to September 21.
This will be a two day event, co-located with Open Source Summit Europe [1].
The LSS-EU CFP is open until Monday, June 5.
Note that announcements relating to the Linux Security Summit may be found
now on the Fediverse, via: https://social.kernel.org/LinuxSecSummit
Best Regards,
Elena Reshetova
[1] https://events.linuxfoundation.org/open-source-summit-europe/
reply other threads:[~2023-04-17 8:35 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=DM8PR11MB57509BF8C3350944A3DB0A8FE79C9@DM8PR11MB5750.namprd11.prod.outlook.com \
--to=elena.reshetova@intel.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-coco@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).