On Tue, 23 Nov 1999, Gerald Abshez wrote: > Here is my 0.02: > > I think it would be useful to identify "unsafe" functions, so that > anyone can participate in the "eyeball" portion of the game. This means > that we need eyeballed, identified as a (potential) problem and fixed, > as well as some other possiblities. There is a lot of code out there, > and it would help if we could involve the non-programmers in the search. > > Comments? Yep, this is part of the "education" component: "this is what an unsafe function call looks like, and this is how to fix it". There's bound to be enough useful documentation out there which we can collect and point to. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Console driver (Was: Re: FreeBSD security auditing ... Ollivier Robert
- Re: FreeBSD security auditing project. Brad Knowles
- Re: FreeBSD security auditing project. Jordan K. Hubbard
- Re: FreeBSD security auditing project. Brad Knowles
- Re: FreeBSD security auditing project. Jordan K. Hubbard
- Re: FreeBSD security auditing project. Michael Kennett
- Re: FreeBSD security auditing project. Kelly Yancey
- Re: FreeBSD security auditing project. Kris Kennaway
- Re: FreeBSD security auditing project. Jordan K. Hubbard
- Re: FreeBSD security auditing project. Gerald Abshez
- Re: FreeBSD security auditing project. Kris Kennaway
- Re: FreeBSD security auditing project. mwlucas
- Re: FreeBSD security auditing proj... Peter Jeremy
- Re: FreeBSD security auditing project. Warner Losh
- Re: FreeBSD security auditing project. Kelly Yancey
- Re: FreeBSD security auditing project. Kelly Yancey
- Re: FreeBSD security auditing project. Tet Solfire
- Re: FreeBSD security auditing project. Warner Losh
- Re: FreeBSD security auditing project. David O'Brien
- Re: FreeBSD security auditing project. Kelly Yancey
- Re: FreeBSD security auditing project. David O'Brien