Date: Sat, 8 Feb 1997 12:42:06 -0500 (EST) From: Brian Tao <taob@risc.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com>, pst@freebsd.org, FREEBSD-SECURITY-L <freebsd-security@freebsd.org> Subject: Don't fulminate, be productive (was Re: Karl fulminates, film at 11. == thanks) Message-ID: <Pine.BSF.3.95.970208123826.17362A-100000@alpha.risc.org> In-Reply-To: <20667.855188567@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Feb 1997, Jordan K. Hubbard wrote:
>
> Thank you, this offer is kindly received. Paul Traina, our
> co-security officer, is currently working on a sign-up roster for a
> more complete code review, a piece of which I and many of the other
> core members have also committed to taking.
What sort of requirements would you insist on for a code reviewer?
I wouldn't mind poking around some code, but how much proficiency do
you need? I can read/write C, but that's like saying "he understands
English" and expecting the person to appreciate Shakespeare. I take
it there is more to this job than replacing all sprintf's with
snprintf's? :)
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970208123826.17362A-100000>