Date: Tue, 15 Aug 2006 00:00:22 -0500 From: "R. Tyler Ballance" <tyler@bleepsoft.com> To: trustedbsd-audit@FreeBSD.org Subject: Darwin work Message-ID: <8C40F149-F305-46DC-A39E-66E26C46822D@bleepsoft.com>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suppose it's worth mentioning here, after talking to rwatson@ a bit about what work needs to be done on openbsm and the audit3 code. I'll be initially starting with the openbsm code of course, but I'll be toying with it more academically in my spurious free time, so I'd be more than happy to accept any help ;) FWIW, I also uploaded notes from rwatson's conversation with me: http://tyler.geekisp.com/doc/openbsm_notes.txt The best plan of attack that we (ok, more him than me) came up with was making the Darwin openbsm code operate in the same manner (the / dev/audit pseudo-device) as the FreeBSD and Linux code, and then work from there. I'm branching the mainline openbsm and audit3 code into my user directory in perforce right now, and I'll be sending the autoconf stub patches there for testing, you'll be able to get the code from: //depot/user/tyler/openbsm/... and //depot/user/tyler/ audit3/... Cheers, - -R. Tyler Ballance Lead Developer, bleep. LLC http://www.bleepsoft.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFE4VTpqO6nEJfroRsRAs7KAJ4n4WbzxJjvz2K67ZfxUOePA6WH9ACfdG1I hFmDQFyLFlISUrj235nOZp8= =ToMT -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8C40F149-F305-46DC-A39E-66E26C46822D>