public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: dnagodra@cisco.com, openembedded-core@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: Re: [OE-core] [PATCH] cve-check-map: Add 'cannot-backport' to status map
Date: Mon, 29 Jul 2024 13:03:11 +0100	[thread overview]
Message-ID: <e1612674aafcad3d3fc08285fe2bf0c6e85c44ec.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240724044412.3343884-1-dnagodra@cisco.com>

On Tue, 2024-07-23 at 21:44 -0700, Dhairya Nagodra via lists.openembedded.org wrote:
> - Sometimes, the difference in the codebase of the fixed CVE's version
>   and the current version of the package is huge.
> - This would make the backporting of the CVE not a feasible option.
> - And due to other dependencies and limitations, the upgrade of the
>   package might not be possible as well.
> - This commit would allow users to add a description via CVE_STATUS and
>   still show the CVE as vulnerable.
> 
> Signed-off-by: Dhairya Nagodra <dnagodra@cisco.com>
> ---
>  meta/conf/cve-check-map.conf | 2 ++
>  1 file changed, 2 insertions(+)

I don't think this status make sense as it is too hard to define. For
one person, a cannot backport might be a patch that doesn't apply
cleanly, all the way through to a patch which would need many hours of
work to correctly apply to an earlier version.

I think this classification would be too arbitrary and depends on the
person's skill set too much.

Cheers,

Richard


      parent reply	other threads:[~2024-07-29 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24  4:44 [PATCH] cve-check-map: Add 'cannot-backport' to status map Dhairya Nagodra
2024-07-29 11:39 ` Dhairya Nagodra -X (dnagodra - E-INFO CHIPS INC at Cisco)
2024-07-29 12:03 ` 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=e1612674aafcad3d3fc08285fe2bf0c6e85c44ec.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dnagodra@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=xe-linux-external@cisco.com \
    /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