On Tue, May 02, 2000 at 11:01:38AM -0700, Linda Walsh wrote:
> "Eric W. Biederman" wrote:
> > What bug does adding two new system calls fix?
> > Aren't we in a deep feature freeze at the moment.
> >
> > It isn't even terribly obvious what they are for.
> > The luid I think I have heard of the sess_id I haven't....
> > What bug does adding these fix?
> ---
> The bug is that any major commercial operating system provides
> at least "C2" or "CAPP" level 'trust' (including MS NT). One of the requirements for this level of 'trust' is that audit actions be able to be
> written corresponding to the appropriate 'authenticated' (as in they
> gave a "password" (literal password or other biometric)). Currently,
> none of the uid values can be guaranteed to remain constant for
> a login session. Thus the luid fix.
Forgive me, this message was quite informative, but how does any of this
qualify this patch as being a bug fix? Something this important seems like it
should incubate as a seperate feature addition, w/ potential later inclusion
into the main kernel sources (along the lines of pcmcia-cs, the ieee1394
code, or whatever).
> and more. The US Dod will "prefer" evaluated systems that
> meet "CAPP" or above by Jan 1, 2001 and "require" such systems
> by July 1, 2002. In accordance with plans for Linux OS world domination,
> infiltration of governments is vital (:-)).
Would the DOD accept a patched Linux kernel working in conjuntion w/
the required utils? Why not offer this patch (and whatever else is needed),
along w/ a _working_ release of OB1 seperately?
> To be on the "preferred"
> list, Linux needs to have the feature set of and be evaluated to meet the
> "Controlled Access Protection Profile". Some of our _*Engineering*_ goals
> are to have CAPP in eval by early 2001 and the LSPP evaluation complete
> by 01, Jul, 2002. It is also SGI's desire that all of this work goes
> into the main Linux base for any and everyone to make use of. Toward
> this effort, we released a 'reference' B1 implementation (non-funcional
> due to removal of code we didn't have full ownership of) on
> http://oss.sgi.com/projects/ob1 from the IRIX/Trusted IRIX source. Our
> hope is that people will take ideas and code and help Linux to get to
> those levels of "trust" (it isn't all kernel work).
I dunno, it seems like you should get the above fully operational before you
start requesting that specialized code be included w/ the mainline kernel.
Alexander
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:10 EST