Re: thoughts on kernel security issues

2005-01-19 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ingo Molnar wrote: > * John Richard Moser <[EMAIL PROTECTED]> wrote: > > >>>There was a kernel-based randomization patch floating around at some >>>point, though. I think it's part of PaX. That's the

Passive-aggressive scheduling to enhance responsiveness?

2005-01-18 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was looking at what happens to responsiveness when CPU usagee goes up and I had an idea about CPU and IO scheduling. Tasks can be grouped by user and nice (and by scheduler type but let's leave SCHED_RR and friends out of this). Let's say that use

Re: Linux Kernel Audit Project?

2005-01-17 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Cox wrote: [...] > There are also people other than Linus who read every single changeset. > I do for one. > Yes but (off the record) you people can't even keep hysterical raisins out of fs/proc/base.c :) [...] - -- All content of all messag

Re: Linux Kernel Audit Project?

2005-01-17 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Cox wrote: > On Llu, 2005-01-17 at 07:40, John Richard Moser wrote: > >>On the same line, I've been graphing Ubuntu Linux Security Notices for a >>while. I've noticed that in the last 5, the number of kernel-r

Re: Linux Kernel Audit Project?

2005-01-17 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adrian Bunk wrote: > On Mon, Jan 17, 2005 at 02:47:32AM -0500, John Richard Moser wrote: > [...] > > What exactly do you want to audit for? > Security holes > If it's only for "ordinary" bugs, that'

Re: Linux Kernel Audit Project?

2005-01-17 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Diego Calleja wrote: > El Mon, 17 Jan 2005 02:40:06 -0500 John Richard Moser <[EMAIL PROTECTED]> > escribió: > > >>-BEGIN PGP SIGNED MESSAGE- >>Hash: SHA1 >> >>On the same line, I've be

Re: Linux Kernel Audit Project?

2005-01-16 Thread John Richard Moser
nough, then you can consider some policy about having the changes audited FIRST before releasing; for now that's just not feasible. Dave Jones wrote: > On Mon, Jan 17, 2005 at 02:17:37AM -0500, John Richard Moser wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 &

Re: Linux Kernel Audit Project?

2005-01-16 Thread John Richard Moser
you think you want to be; other times this is arbitrary code execution from inside the kernel and it doesn't matter who the kernel thinks you are, you're in control. Oh well, at least they still get fixed when they're seen. John Richard Moser wrote: > Is there an official Linux Ker

Linux Kernel Audit Project?

2005-01-16 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there an official Linux Kernel Audit Project to actively and aggressively security audit all patches going into the Linux Kernel, or do they just get a cursory scan for bugs and obvious screwups? - -- All content of all messages exchanged herein are

Re: /proc//maps API addition - seek to address

2005-01-16 Thread John Richard Moser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Fitzhardinge wrote: > It would be terribly useful to have some way of > lseeking /proc//maps to the entry of a particular address. So, if > you want to find the information about a mapping containing address > 0x12345678, it would set the fil

<    1   2