All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clay Montgomery" <clay@montgomery1.com>
To: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Kernel support for i.MX6UL and 4.9 LTS updates
Date: Thu, 9 Jan 2020 15:26:58 -0600	[thread overview]
Message-ID: <814fa807-bcdd-43b9-174a-0e313a6f3765@montgomery1.com> (raw)
In-Reply-To: <CAP9ODKrZ2+TnaLJtq0p=0h=-8uOkEYPpYMp9qDCYctP_f6-0jg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]


On 1/9/2020 2:14 PM, Otavio Salvador wrote:
> On Thu, Jan 9, 2020 at 5:08 PM Jesse Gilles <jesse.gilles@gmail.com> wrote:
>> On Thu, Jan 9, 2020 at 11:18 AM Clay Montgomery <clay@montgomery1.com> wrote:
>> Hm, I don't agree.  If an embedded Linux device uses Wi-Fi and Bluetooth communications, won't vulnerabilities affecting those parts of the kernel need to be patched?
>>
>> Examples:
>> https://www.linuxkernelcves.com/cves/CVE-2019-17133
>> https://www.linuxkernelcves.com/cves/CVE-2019-16746
>> https://www.linuxkernelcves.com/cves/CVE-2019-9506
>>
>> I believe some of these could be exploitable without accessing the device or gaining local privileges.
> I agree with you Jesse and that's why we've been moving most of our
> customers to Linux mainline. Most vendor BSP does not have stable
> updates.
>
It depends in your target application/market. If anyone can connect to 
your device with Wi-Fi or Bluetooth, then obviously security is a lot 
more important.

But, consider the digital signage player market, for example, where it's 
actually an advantage over Windows and Android devices to never require 
updates.

Regards, Clay


> 

[-- Attachment #2: Type: text/html, Size: 2431 bytes --]

  reply	other threads:[~2020-01-09 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 22:33 Kernel support for i.MX6UL and 4.9 LTS updates jesse.gilles
2019-12-21 12:11 ` [meta-freescale] " Fabio Estevam
2020-01-03 19:40   ` Jesse Gilles
2020-01-03 22:21     ` Clay Montgomery
2020-01-09 15:13       ` Jesse Gilles
2020-01-09 15:28         ` Richard Leitner
2020-01-09 20:14           ` Jesse Gilles
2020-01-10  7:46             ` Richard Leitner
2020-01-09 17:18         ` Clay Montgomery
2020-01-09 20:08           ` Jesse Gilles
2020-01-09 20:14             ` Otavio Salvador
2020-01-09 21:26               ` Clay Montgomery [this message]
2020-01-04 15:31     ` Fabio Estevam

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=814fa807-bcdd-43b9-174a-0e313a6f3765@montgomery1.com \
    --to=clay@montgomery1.com \
    --cc=meta-freescale@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.