All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Lee, Chee Yang" <chee.yang.lee@intel.com>,
	Ross Burton <ross@burtonini.com>
Cc: Steve Sakoman <steve@sakoman.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	 "yocto-security@lists.yoctoproject.org"
	<yocto-security@lists.yoctoproject.org>
Subject: Re: [OE-core] [yocto-security] OE-core CVE metrics for master on Sun 24 Jan 2021 07:15:01 AM HST
Date: Tue, 26 Jan 2021 16:55:06 +0000	[thread overview]
Message-ID: <332c0f30e9d8ff14bda4bbb0aadbbda7ecdcc606.camel@linuxfoundation.org> (raw)
In-Reply-To: <MWHPR11MB200003E4ED93C922C896F758B9BC9@MWHPR11MB2000.namprd11.prod.outlook.com>

On Tue, 2021-01-26 at 16:19 +0000, Lee, Chee Yang wrote:
> A variable in recipe to indicate the character as patch level?
> like CVE_VERSION_SUFFIX  in  “alphabetical”  so the parser understand
> the last alphabetical character as patched release

Something like that could work. We really need to handle openssl
versioning in particular so we need to do something (or revert the
change if we can't fix it).

Cheers,

Richard


      reply	other threads:[~2021-01-26 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 17:18 OE-core CVE metrics for master on Sun 24 Jan 2021 07:15:01 AM HST Steve Sakoman
2021-01-24 23:20 ` [yocto-security] " Richard Purdie
2021-01-25  2:39   ` Lee Chee Yang
2021-01-25 22:10     ` Richard Purdie
2021-01-26  3:54       ` Lee Chee Yang
2021-01-26  9:54         ` [OE-core] " Ross Burton
2021-01-26 16:19           ` Lee Chee Yang
2021-01-26 16:55             ` Richard Purdie [this message]

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=332c0f30e9d8ff14bda4bbb0aadbbda7ecdcc606.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chee.yang.lee@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.com \
    --cc=steve@sakoman.com \
    --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.