From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 1/2] nss: Move to meta-oe
Date: Wed, 4 Mar 2020 11:05:07 +0200 [thread overview]
Message-ID: <20200304090507.GA7923@localhost> (raw)
In-Reply-To: <CANNYZj8zWJVwAz+N3ikC+bw7iJba7OVbCs0dTsZgNo_PRkrY3A@mail.gmail.com>
On Thu, Feb 27, 2020 at 03:03:18PM +0100, Alexander Kanavin wrote:
> On Thu, 27 Feb 2020 at 14:28, Adrian Bunk <bunk@stusta.de> wrote:
>
> > >...
> >
> > It is a crypto library with a history of unfixed CVEs in supported
> > stable Yocto releases.
> >
>
> If the issue is unfixed CVEs, then I do not think it's particularly
> relevant which layer the recipe is in. Stable release maintainers are not
> expected to 'track and fix CVEs', that one is on users.
Yesterdays LTS announcement makes it clear that the Yocto project does
provide regular security updates for supported stable branches:
<-- snip -->
Yocto Project releases are usually maintained for one year.
Beyond this period, releases move to community support, which means
they only receive occasional patches for critical defects and updates,
and no regular defect fixes and security updates.
<-- snip -->
> Alex
cu
Adrian
next prev parent reply other threads:[~2020-03-04 9:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 19:34 [RFC][PATCH 1/2] nss: Move to meta-oe Adrian Bunk
2020-02-23 19:34 ` [RFC][PATCH 2/2] nspr: " Adrian Bunk
2020-02-24 0:25 ` [RFC][PATCH 1/2] nss: " Khem Raj
2020-02-24 5:17 ` Adrian Bunk
2020-02-24 16:32 ` akuster808
2020-02-27 13:27 ` Adrian Bunk
2020-02-27 14:03 ` Alexander Kanavin
2020-03-04 9:05 ` Adrian Bunk [this message]
2020-03-04 9:36 ` Alexander Kanavin
2020-03-04 11:32 ` Adrian Bunk
2020-03-04 12:13 ` Alexander Kanavin
2020-03-04 14:01 ` Does YP provide security support for stable and LTS branches? Adrian Bunk
2020-03-04 16:00 ` Alexander Kanavin
2020-03-04 17:24 ` Adrian Bunk
2020-03-04 20:26 ` [Openembedded-architecture] " akuster808
2020-03-06 10:04 ` Adrian Bunk
2020-03-06 10:36 ` Richard Purdie
2020-03-08 21:46 ` Adrian Bunk
2020-03-08 22:08 ` Alexander Kanavin
2020-03-09 0:23 ` Adrian Bunk
2020-03-09 7:29 ` Ayoub Zaki
2020-03-09 9:53 ` Alexander Kanavin
2020-03-09 12:45 ` Richard Purdie
2020-03-10 16:11 ` Ross Burton
2020-03-10 19:45 ` Ayoub Zaki
2020-03-11 14:53 ` Ross Burton
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=20200304090507.GA7923@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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