From: "Steve Sakoman" <steve@sakoman.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
yocto-security@lists.yoctoproject.org
Subject: Re: [yocto-security] OE-core CVE metrics for hardknott on Sun 12 Sep 2021 05:00:01 AM HST
Date: Sun, 12 Sep 2021 06:04:54 -1000 [thread overview]
Message-ID: <CAOSpxdZG9Uh6G4+9f3gR6AGH=OfV4rA04xhLuo+h1-7GtfNyEg@mail.gmail.com> (raw)
In-Reply-To: <d6ad55b4fdcca27eee438031ea60b586c0f7f9da.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Sun, Sep 12, 2021, 5:57 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Sun, 2021-09-12 at 05:01 -1000, Steve Sakoman wrote:
> > Branch: hardknott
> >
> > New this week: 0 CVEs
> >
> > Removed this week: 2 CVEs
> > CVE-2020-27748: xdg-utils
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27748 *
> > CVE-2021-38185: cpio
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-38185 *
>
> I'm not sure I believe these numbers as tar CVEs which showed up for
> dunfell and
> master don't show up here. Why? :/
>
Don't know! Will investigate tomorrow.
Steve
> Cheers,
>
> Richard
>
>
[-- Attachment #2: Type: text/html, Size: 1526 bytes --]
next prev parent reply other threads:[~2021-09-12 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 15:01 OE-core CVE metrics for hardknott on Sun 12 Sep 2021 05:00:01 AM HST Steve Sakoman
2021-09-12 15:57 ` [yocto-security] " Richard Purdie
2021-09-12 16:04 ` Steve Sakoman [this message]
[not found] ` <16A41EB09718E439.21276@lists.openembedded.org>
2021-09-13 15:19 ` [OE-core] " Steve Sakoman
2021-09-13 17:01 ` Richard Purdie
2021-09-13 17:26 ` Steve Sakoman
2021-09-15 11:08 ` Ross Burton
2021-09-15 14:09 ` Steve Sakoman
2021-09-15 16:58 ` [OE-core] " Anuj Mittal
2021-09-15 17:03 ` Steve Sakoman
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='CAOSpxdZG9Uh6G4+9f3gR6AGH=OfV4rA04xhLuo+h1-7GtfNyEg@mail.gmail.com' \
--to=steve@sakoman.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto-security@lists.yoctoproject.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.