Return-Path: Received: from mailrelay4-3.pub.mailoutpod1-cph3.one.com (mailrelay4-3.pub.mailoutpod1-cph3.one.com [46.30.212.13]) by mail.openembedded.org (Postfix) with ESMTP id EAA8061024 for ; Tue, 10 Mar 2020 19:45:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=embexus.com; s=20191106; h=content-type:in-reply-to:mime-version:date:message-id:from:references:cc:to: subject:from; bh=tuz9f10FgbkICZ1h3/nIrAq1BBb82L0K4CdJToubXyo=; b=jS0c2CYbw1zpYkDJkoEodokfE202rFLjcjG1HJ80eHArarRZTqnxnW2z9oCL+8lAH/wakqexSF/R7 F4iCsH/PbiXUHXMHH8KXZNCrsOK+JjFZUXVC5NcP50nNXuLMhRDL0FERIIicp5uHnfz9vz78AkS3sN WFMBA4u8EH0OWV7Rg7x5uoZvONPLUqjUG2W5X+k8HNTdANZL5pAk+4Z5vzGvnNP1+1fhrLD8ti0Vj/ uyfmicAP7ZsYWB7O98dCqn8s2i7IlsU5BE3n68zLkjH8mEv+vJJwFclRh0++QjKulgO/rBlMUehVxC KXlsK+WckbRwb7UYWqd0IAavZvgJAkQ== X-HalOne-Cookie: 83e3fd4dcc6ddd282998d5672add5a0a613f9291 X-HalOne-ID: c34d8c9c-6307-11ea-8c79-d0431ea8bb10 Received: from [192.168.178.22] (x4db4211c.dyn.telefonica.de [77.180.33.28]) by mailrelay4.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id c34d8c9c-6307-11ea-8c79-d0431ea8bb10; Tue, 10 Mar 2020 19:45:58 +0000 (UTC) To: Ross Burton References: <20200304113217.GB7923@localhost> <20200304140109.GC7923@localhost> <20200304172415.GA29456@localhost> <01b3bb37-f65f-8048-1a27-b859b62d7f98@gmail.com> <20200306100422.GA17785@localhost> <877e317932176664bc7b0120439c56d4dda791af.camel@linuxfoundation.org> <20200308214610.GB1425@localhost> <20200309002308.GD1425@localhost> From: Ayoub Zaki Message-ID: <1c4e1685-7b74-0dea-e08f-4887fca9eb66@embexus.com> Date: Tue, 10 Mar 2020 20:45:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Cc: OE-core Subject: Re: [Openembedded-architecture] Does YP provide security support for stable and LTS branches? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2020 19:45:59 -0000 Content-Type: multipart/alternative; boundary="------------DCE532143784B84DB660F8CB" Content-Language: en-US --------------DCE532143784B84DB660F8CB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, On 10.03.20 17:11, Ross Burton wrote: > On Mon, 9 Mar 2020 at 07:45, Ayoub Zaki wrote: >> Adrian is making a point here, The Yocto Project by claiming that it >> supports security patches for Stable releases is misleading the Users! >> >> I work with different customers and some of them think that by using and >> pulling the latest releases they will get the CVEs automatically fixed! >> >> YP should state that CLEARLY! Of course it will impact the choice of >> going with Yocto or Not ( probably NOT in this case). > What would the alternative to Yocto be, and what is their security > policy? Does e.g. buildroot commit to fixing every known security > issue (which is more than just known CVEs) in their releases? Security patches support is definitely for many companies a knock-out criterion. Probably in this case Debian or a commercial OSes like Qnx would be a choice for who can afford it. Mit freundlichen Grüßen / Kind regards -- Ayoub Zaki Embedded Systems Consultant Vaihinger Straße 2/1 D-71634 Ludwigsburg Mobile : +4917662901545 Email : ayoub.zaki@embexus.com Homepage : https://embexus.com VAT No. : DE313902634 --------------DCE532143784B84DB660F8CB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi,


On 10.03.20 17:11, Ross Burton wrote:
On Mon, 9 Mar 2020 at 07:45, Ayoub Zaki <ayoub.zaki@embexus.com> wrote:
Adrian is making a point here, The Yocto Project by claiming that it
supports security patches for Stable releases is misleading the Users!

I work with different customers and some of them think that by using and
pulling the latest releases they will get the CVEs automatically fixed!

YP should state that CLEARLY! Of course it will impact the choice of
going with Yocto or Not ( probably NOT in this case).
What would the alternative to Yocto be, and what is their security
policy?  Does e.g. buildroot commit to fixing every known security
issue (which is more than just known CVEs) in their releases?


Security patches support is definitely for many companies a knock-out criterion.
Probably in this case Debian or a commercial OSes like Qnx would be a choice for who can afford it.


Mit freundlichen Grüßen / Kind regards

-- 
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg


Mobile   : +4917662901545
Email    : ayoub.zaki@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634
--------------DCE532143784B84DB660F8CB--