On 12/30/2010 07:39 PM, ext Arjan van de Ven wrote:
Now that we're on a much more recent upstream kernel... your security
patches should be much much less, right?
(and already been discussed upstream etc)
Most are in security-testing, but we're not sure if creds will
ever be there. We shall see that. Anyway, we need it to maintain
compatibility with existing applications and there _is_ potential
in it for generic security API (GREAT thing should it work out
in the end). Your advice?
Anyway, now that creds seems 'ready', I will post it upstream for
first comments. May be a rough ride but still.
How do we deal with config
changes?
compliance will specify a minimum required set, the rest is up to the
adaptation owner.
Ok but I was interested in the security ones and I take those
have to go to the reference kernel. Should I just send you a
config fragment or how does this go?
--
// Janne
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
