On Thursday 15 March 2007 21:58, M Harris wrote:
No, what I am saying is that running a back-level linux kernel is not a problem. As far as updating user apps goes... that depends on the app.
It depends. There have been issues. I remember one issue about the TCP stack leaking kernel memory, which meant people could potentially see data they weren't supposed to see. And there have been some DoS problems But yes, by far the most kernel problems are local exploits. The problem is that when you run applications that have holes that allow attackers to run a local program, combined with a local exploit in the kernel, then you have a problem.
My Firefox updates automatically... and aside from the slightly annoying message telling me the update is available its pretty painless... it has always worked, and it has been completely automatic... wish I could say the same thing for the Suse updater... :-(
The firefox updater is a glorified wget. The suse updater needs to do a lot more. Not that I'm defending the current state of the updater, it still needs a lot of work - but comparing with the firefox updater is just silly
No, the original thought was ridiculous--- running a back-level version of the linux kernel is not a problem... and as for that matter... running a patched version of apps (back-level as they may be) is not a problem either...
The problem might be in getting the patches. There is a lot of work involved
in fact... some might argue that updating apps and kernels is how vulnerabilities are introduced into systems in the first place.
Really? Who? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org