Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-architecture@lists.openembedded.org,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Does YP provide security support for stable and LTS branches?
Date: Wed, 4 Mar 2020 19:24:15 +0200	[thread overview]
Message-ID: <20200304172415.GA29456@localhost> (raw)
In-Reply-To: <CANNYZj8ciqgR7eed+B+WwfMRHKc3u_XHrT3vo004=TEX9cCmhA@mail.gmail.com>

On Wed, Mar 04, 2020 at 05:00:44PM +0100, Alexander Kanavin wrote:
> Taking offense or getting angry at the yocto project is entirely
> misdirected.

I am not angry if YP does not provide security support.

I am angry when YP is telling lies that it would provide security 
support, but does not actually provide it.

> The liability for insecure millions of devices does not lie
> with the yocto project, it lies with the OEMs.
>...

The liability for insecure millions of devices lies 100% with the Yocto 
Project if it claims to provide security support but does not actually 
provide it.

If a user has to decide today whether an upcoming product will run
Ubuntu 20.04 LTS or Yocto 3.1 LTS, then it should be clear to the
user whether or not choosing Yocto will provide upstream security 
support the same way as Ubuntu.

A user reading the YP LTS announcement expects security support similar 
to what Ubuntu is offering, and might only notice that this isn't true 
after a known vulnerability gets exploited on millions of devices.

If security support for YP stable and LTS releases is only on a
community support basis and usually incomplete, then it is on YP
to make that clear to all users instead of claiming the opposite - in 
other projects LTS does include security support, sometimes only 
security fixes are permitted.

This could be combined with a call for help for security support,
an advantage of being honest would be that it becomes visible for
users that there is a resource shortage.

> Alex

cu
Adrian


  reply	other threads:[~2020-03-04 17:24 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
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 [this message]
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=20200304172415.GA29456@localhost \
    --to=bunk@stusta.de \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --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