In message <[EMAIL PROTECTED]> Kris Kennaway writes: : 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. __warn_references(tempnam, "warning: tempnam() possibly used unsafely; consider using mkstemp()"); We can increase the number of functions that have this tag (maybe optionally to aid in the search). However, tagging strcpy may produce too loud a cacophony to be useful. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- 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
- Re: FreeBSD security auditing project. Rodney W. Grimes
- Re: FreeBSD security auditing project. Alexey Zelkin
- Re: FreeBSD security auditing project. Warner Losh