All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Joseph Reynolds <jrey@linux.ibm.com>, openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday January 19
Date: Wed, 19 Jan 2022 11:00:49 -0500	[thread overview]
Message-ID: <2307.1642608049@localhost> (raw)
In-Reply-To: <c8c1bdcb-bf8a-c266-53c2-51f53fbe44ea@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]


Joseph Reynolds <jrey@linux.ibm.com> wrote:
    > We'll discuss the following items on the agenda
    > <https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>,
    > and anything else that comes up:

I went through the effort to become a CNA for tcpdump.org.
Lots of stupid marketing overhead as mitre thinks they need to tell your
marketing people what it's about :-(

It took me many tries to generate a valid JSON file for my CVE reports, but I
did finally get it.  Unicast me when you get there if you need help.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 398 bytes --]

  reply	other threads:[~2022-01-19 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  4:03 Security Working Group meeting - Wednesday January 19 Joseph Reynolds
2022-01-19 16:00 ` Michael Richardson [this message]
2022-01-19 18:36 ` Security Working Group meeting - Wednesday January 19 - results Joseph Reynolds

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=2307.1642608049@localhost \
    --to=mcr@sandelman.ca \
    --cc=jrey@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.