From: Greg KH <gregkh@linuxfoundation.org>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jiri Kosina <jikos@kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Handling of embargoed security issues -- security@korg vs. linux-distros@
Date: Fri, 16 Feb 2024 18:34:37 +0100 [thread overview]
Message-ID: <2024021634-starlit-waviness-c329@gregkh> (raw)
In-Reply-To: <20240216171427.GA9244@kitsune.suse.cz>
On Fri, Feb 16, 2024 at 06:14:27PM +0100, Michal Suchánek wrote:
> On Wed, Aug 16, 2023 at 04:55:39PM +0200, Greg KH wrote:
That was a very old thread, why dig it up now?
> > Together we were able to solve the "impossible" problem of Android
> > kernel security. Now that that windmill is semi-successfully conquered
> > despite many who thought it never could be, why can't we help other
> > users of our product to do the same? If not, we run the risk of having
> > Linux be blamed for bad security, when in reality, it's the policy of
> > companies not taking advantage of what we are providing them, a nuance
> > that Linux users will never really understand, nor should they have to.
>
> The real impossible problem of Android security is that those Android
> systems aren't really opensource, and it's (next to) impossible to get
> updataes when the device vendor does not provide one.
>
> So many Android device users are running long-obsolete systems because
> there is nothing more recent that runs on their device.
>
> That won't change no matter what stable does or does not.
That is why governments are making laws to require this to happen. The
EU just did this for all mobile devices, and I expect other governments
to do the same over time.
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-16 17:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 9:28 [MAINTAINERS SUMMIT] Handling of embargoed security issues -- security@korg vs. linux-distros@ Jiri Kosina
2023-08-15 10:17 ` Vegard Nossum
2023-08-15 10:34 ` Jiri Kosina
2023-08-15 11:23 ` Greg KH
2023-08-15 12:42 ` Steven Rostedt
2023-08-15 13:17 ` Daniel Borkmann
2023-08-15 14:19 ` Laurent Pinchart
2023-08-15 22:04 ` Jiri Kosina
2023-08-15 14:20 ` Catalin Marinas
2023-08-15 14:41 ` Greg KH
2023-08-15 15:04 ` Steven Rostedt
2023-08-15 15:51 ` Greg KH
2023-08-15 15:08 ` Greg KH
2023-08-15 18:46 ` Konrad Rzeszutek Wilk
2023-08-15 19:41 ` Greg KH
2023-08-15 22:13 ` Jiri Kosina
2023-08-15 22:31 ` Steven Rostedt
2023-08-16 14:55 ` Greg KH
2024-02-16 17:14 ` Michal Suchánek
2024-02-16 17:34 ` Greg KH [this message]
2024-02-16 18:13 ` Michal Suchánek
2024-02-16 18:16 ` Jiri Kosina
2023-08-15 22:17 ` Jiri Kosina
2023-08-16 14:57 ` Greg KH
2023-08-16 17:22 ` Jiri Kosina
2023-08-16 18:38 ` Vegard Nossum
2023-08-16 15:26 ` Solar Designer
2023-08-25 11:17 ` Donald Buczek
2023-08-29 8:46 ` Miroslav Benes
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=2024021634-starlit-waviness-c329@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=msuchanek@suse.de \
--cc=rostedt@goodmis.org \
--cc=vegard.nossum@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).