In message <[EMAIL PROTECTED]> Peter Jeremy writes: : I suspect that a 'cvs diff' of the OpenBSD code tree is the best : starting point. As a veteran of that war, I think you underestimate that task be about a few orders of magnitude. A better starting point I've found to be the ChangeLog files in the CVSROOT directory of the openbsd tree. After a while, you get a good nose for reading them to know what is important and what isn't. Once you hit a program that has had one fix, it is most productive, I've found, to integrate all the security and bug fixes things you can find in that program, and then reaudit the hell of out of it in case you introduce something bogus. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: FreeBSD security auditing project. Christopher Nielsen
- Re: FreeBSD security auditing project. Kris Kennaway
- Re: FreeBSD security auditing project. Peter Jeremy
- Re: FreeBSD security auditing project. Kris Kennaway
- Re: FreeBSD security auditing proje... David O'Brien
- Re: FreeBSD security auditing p... Kris Kennaway
- Re: FreeBSD security auditing p... Peter Jeremy
- Re: FreeBSD security auditing p... Jordan K. Hubbard
- Re: FreeBSD security audit... Peter Jeremy
- Re: FreeBSD security audit... David O'Brien
- Re: FreeBSD security auditing p... Warner Losh
- Re: FreeBSD security auditing project. Brian Fundakowski Feldman
- Re: FreeBSD security auditing proje... Peter Jeremy
- Re: FreeBSD security auditing p... Brian Fundakowski Feldman
- Re: FreeBSD security audit... Brad Knowles
- Re: FreeBSD security auditing proje... Jordan K. Hubbard
- Re: FreeBSD security auditing proje... Warner Losh
- Re: FreeBSD security auditing proje... Warner Losh
- Re: FreeBSD security auditing proje... Garrett Wollman
- Re: FreeBSD security auditing p... Michael Kennett
- Re: FreeBSD security auditing project. Mark Murray