Obtaining 2.6.8-1.541 source code

[Matthew Miller]

On Tue, Sep 14, 2004 at 03:47:01PM -0500, Gregory G Carter wrote:
> For one thing, it makes no sense to have any OS code running outside of 
> a primary security or root zone.  With the possible exception of 
> virtualizing the kernel source/binaries under a execution context.  
> (i.e. vmware, UML...etc).

I think you're confusing "running" and "building". There's no reason to
_ever_ run a compiler as root.

This is just generally good security practice -- use only the highest level
of privledge required. If you don't need to be root to do something, don't
be.


> I would be OK with that as long as user space edits of the kernel where 
> only distributed as binaries in root space.

And I'm not even sure this sentence makes any sense. :)


> But, having as you suggest a user space kernel tree from which to 
> maintain system intergrity, binary or otherwise in building a system I 
> think is fool hardy.
> You should have a source tree that is in root space that is seperate 
> from user space.

I don't see any advantage in this at all. However, if you want to create a
separate "rpmbuilder" account in which you build your packages, fine -- but
there's absolutely no reason to give it root privileges.


> The root space is a reference point for compiling system software, in a 
> predictable security context.  (i.e. root.)

Root is *less* predictable. That's the point.




-- 
Matthew Miller           mattdm at mattdm.org        <http://www.mattdm.org/>
Boston University Linux      ------>                <http://linux.bu.edu/>