public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: cert+donotreply@cert.org
To: gcc@gcc.gnu.org
Subject: [gen-14164] Invitation to the CERT Vendor Meeting 2022
Date: Fri, 7 Jan 2022 20:14:41 +0000	[thread overview]
Message-ID: <0100017e362dd9de-065f8c99-4403-43f7-b08c-098f0ff99855-000000@email.amazonses.com> (raw)

We invite you to join us for the CERT Vendor Meeting 2022. This will be a virtual event, 2022-02-07 10:00-14:30 EST, via Zoom Webinar.

We'll be discussing two topics in some depth, using an extended panel format (short presentations, moderated discussion, open discussion).

Topic 1: Log4j, a multi-party coordinated vulnerability disclosure failure?

Topic 2: There's no such thing as free software, or, how to invest in OSS security.

Registration: <https://cert-vendor-meeting-2022-feb.eventbrite.com>

Questions: <vul-event-rsvp@cert.org>



    
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-01-07 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 20:14 cert+donotreply [this message]
2022-01-07 20:18 ` Toon Moene

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=0100017e362dd9de-065f8c99-4403-43f7-b08c-098f0ff99855-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).