Re: Only auditing current 2.4 code?

[Gigi Sullivan <sullivan@sikurezza.org>]

Aiee :)

	Hello!

> 
> 	I'm quite new to programming and never done a code audit before,
> but I had a thought.  Darron suggests below (as others have as well) that
> this project focus on the 2.2.x or earlier kernels as they are more
> stable.  Could it be more advantageous to work on the 2.4.x kernels
> BECAUSE they are in a state of flux?  Would the kernel hackers be more
> willing to incorporate changes in them now while they're still tinkering
> in the bowels of the code?  Although an audit of the stable kernels would
> make our job easier, would the kernel hackers (who are going to be
> focusing on the 2.4.x kernels) going to be as willing to patch a stable
> kernel that fewer people are working on, with code that might break
> something else at a higher level?

	This sounds good and it's right, however keep in mind that LOTS of 
	people won't upgrade their kernel when the new one will be out 
	(really out) for several reason that are pointless stated here.

	I guess we should concentrate our work on both kernel 2.2.X series
	and 2.4.X ones, with particoular care about the former, IMHO.

	Nevertheless to say that the current new kernel should not be put
	in a corner ...

> 
> IMHO,
> Stephan
> 

bye bye

			-- gg sullivan

-- 
Lorenzo Cavallaro	`Gigi Sullivan' <sullivan@sikurezza.org>

Until I loved, life had no beauty;
I did not know I lived until I had loved. (Theodor Korner)

Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/