To the contrary, the work was done by the NSA.
If you look at the Contributors page, you'll
see the breakdown of who did what in developing
the Security-Enhanced Linux. As far as its
predecessors go, the Flask prototype was
developed entirely by the NSA and the University
of Utah, with most of the security development by the NSA. Secure Computing simply provided technical review and some assurance work. For DTOS, Secure Computing was GIVEN a working prototype of the security-enhanced Mach microkernel and a security server by the NSA, and they then did a clean re-implementation with some simultaneous assurance work. Meanwhile, the NSA did the security development for the Lites Unix single server that ran on the microkernel, including security enhancements to the file system, networking, and process management code.
How do I know this? Because I worked on DTOS, Flask, and the Security-Enhanced Linux.
Slashdot Mirror
To the contrary, the work was done by the NSA. If you look at the Contributors page, you'll see the breakdown of who did what in developing the Security-Enhanced Linux. As far as its predecessors go, the Flask prototype was developed entirely by the NSA and the University of Utah, with most of the security development by the NSA. Secure Computing simply provided technical review and some assurance work. For DTOS, Secure Computing was GIVEN a working prototype of the security-enhanced Mach microkernel and a security server by the NSA, and they then did a clean re-implementation with some simultaneous assurance work. Meanwhile, the NSA did the security development for the Lites Unix single server that ran on the microkernel, including security enhancements to the file system, networking, and process management code. How do I know this? Because I worked on DTOS, Flask, and the Security-Enhanced Linux.