From: cert+donotreply@cert.org
To: gcc@gcc.gnu.org
Subject: [gen-16862] Invitation to the CERT Vendor Meeting 2022 (June 6)
Date: Fri, 29 Apr 2022 17:43:13 +0000 [thread overview]
Message-ID: <01000180766b6e9e-4794caec-0e0c-4b26-8ea4-3450a47da7a9-000000@email.amazonses.com> (raw)
While it's unusual for us to hold meetings so close together, it's been an unusual couple of years, and we are holding a full day, hybrid event on June 6 2022, the Monday of RSAC 2022. The meeting will be held from 9 AM to 5 PM PDT, in person at the Marriott Marquis in San Francisco, CA, US, and online via Zoom Webinar.
Register here: <https://cert-vendor-meeting-2022-jun.eventbrite.com/>
Registration options include in-person, virtual, or both.
Questions/issues about registration, logistics, etc: <vul-event-rsvp@cert.org>
Topical discussion: <vendor-meetings@cert.org>
We actively seek ideas for topics that are of interest to you, and we welcome those wishing to speak or lead a discussion topic or participate on a panel. The draft/working list topics includes:
* UEFI vulnerability analysis
* Linux Vendor Firmware Service (LVFS), possibly connected to the UEFI topic, probably also with supply chain/SBOM implications
* A CVD protocol
* CVE
* SBOM, VEX
* Government regulations impacting CVD
While we're more or less happy to decide the agenda ourselves, we'd be happier with your input, and you might be too.
Regards,
- Art
This e-mail was sent to you as a user of our VINCE service, in accordance with our privacy policy. Please advise us if you believe you have received this e-mail in error.
reply other threads:[~2022-04-29 17:43 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=01000180766b6e9e-4794caec-0e0c-4b26-8ea4-3450a47da7a9-000000@email.amazonses.com \
--to=cert+donotreply@cert.org \
--cc=gcc@gcc.gnu.org \
/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).