This is a discussion on Merits of TrustedBSD for OpenBSD within the mailing.openbsd.tech forums, part of the OpenBSD category; --> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy, I've started toying with bringing openbsm[1] and the audit3[2] code from the ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy, I've started toying with bringing openbsm[1] and the audit3[2] code from the TrustedBSD project up to speed on Darwin and I'm wondering why the OpenBSD project hasn't started adopting some of the code and merging it into a sort of TrustedAndOpenBSD project A couple of the things I think OpenBSD could greatly benefit from, such as the MAC framework, access control lists, and then of course, the auditing that OpenBSD and the auditing code in the kernel allows. I'm certain that this would be a great amount of work, so I'm asking more if somebody's already started, while I dont' really have time to contribute code, I'd be more than happy to test the code. I see absolutely no feasible reason why OpenBSD should be satisfied with being "really secure", merging some of the improvements brought by TrustedBSD seems like a viable way to make OpenBSD a "really really super duper secure" OS Thoughts? Has anybody started at least working on say, access control lists? (something I'm sure NetBSD would like to have as well) Cheers, - -R. Tyler Ballance Lead Developer, bleep. LLC http://www.bleepsoft.com iD8DBQFE4Xk9qO6nEJfroRsRAsIIAKCEYcDVN3yAuyj6eZWgjE W351am7ACeOmqY t+jI8KVTVHYTiJJALMd17+A= =Hs7h -----END PGP SIGNATURE----- |