sample 5.3 based trusted os ;-)

Eric Hall trustedbsd at ghosthound.net
Thu Jan 20 22:00:48 GMT 2005


On Thu, Jan 20, 2005 at 11:15:33AM +0000, Ilmar S. Habibulin wrote:
> 
> 
> On Thu, 20 Jan 2005, Robert Watson wrote:
> 
> > I've talked to Gordon Tetlow who helps run the Perforce server, and he
> > indicated that cvsup export was turned off in June for some reason, and
> > he's going to talk to Peter Wemm to figure out why.  Assuming all goes
> > well, and the reason wasn't really a good one (i.e., upgrade in progress)
> > it should be back on in another day or two, and will also export audit3.
> > Sorry about that!
> Cvsup is not the only way to grab the source. But it simplifies many
> things ;-) Btw, what about capabilities branch? The idea was great, and i
> think that community will accept it more easily that mandatory access
> control. SEBSD is much more flexible, and this flexibility is the main
> problem, imho, because it prevent much wider use of this policy. It's not
> so simple as capabilities are, and capabilities can be integrated in the
> base system. And can be setup by default insted of SUID bits. Just add
> some archiver with extended attributes support. I've included in my
> trustedos Thomas Moestl's hacked tar from trustedbsd-cap branch. This is
> old version of gnu tar, because i was unable to port his changes to the
> newer one.
> 

	There is an archiver that understands (FreeBSD) EAs, 'xar',
available at:

	http://www.opendarwin.org/projects/xar/

	I bounced it off the developers, they say it currently works.
Beyond that, I have no idea if its suitable for inclusion or not.


		HTH,


		-eric

To Unsubscribe: send mail to majordomo at trustedbsd.org
with "unsubscribe trustedbsd-discuss" in the body of the message



More information about the trustedbsd-discuss mailing list