linux-kernel - Re: Future of the -longterm kernel releases (i.e. how we pick them).

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Aug 2011 16:57:44 -0700
From:	Greg KH <greg@...ah.com>
To:	Daniel Taylor <Daniel.Taylor@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Future of the -longterm kernel releases (i.e. how we pick them).

On Mon, Aug 15, 2011 at 10:26:54PM -0700, Daniel Taylor wrote:
> For embedded systems, which often have multi- (not just two-) year
> warranties, it sounds like we would then be maintaining the -longterm
> ourselves.  The "easy" side of this is that embedded systems don't
> (usually) have users trying to plug in the latest and greatest widget,
> except on external busses, such as USB.  So back-porting drivers is
> not generally a big deal.  Security patches, OTOH, are a real concern.
> Other than net and drivers/net, which are exposed to non-local attacks,
> are there other subsystems we should watch for security fixes?  There
> have, for example, been a lot of security upgrades in /sys, but there's
> also been a lot of restructing for new interfaces and "arch" models,
> which would make back-porting those much more complicated.

You should watch out for all bugfixes, that's the only way to have a
chance at catching all of the issues.

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/