From owner-freebsd-security Sat Feb 8 09:43:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21878 for security-outgoing; Sat, 8 Feb 1997 09:43:49 -0800 (PST) Received: from alpha.risc.org (trt-on7-45.netcom.ca [207.181.82.173]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21843; Sat, 8 Feb 1997 09:42:28 -0800 (PST) Received: from localhost (taob@localhost) by alpha.risc.org (8.8.4/8.8.4) with SMTP id MAA17372; Sat, 8 Feb 1997 12:42:07 -0500 (EST) Date: Sat, 8 Feb 1997 12:42:06 -0500 (EST) From: Brian Tao To: "Jordan K. Hubbard" , pst@freebsd.org, FREEBSD-SECURITY-L Subject: Don't fulminate, be productive (was Re: Karl fulminates, film at 11. == thanks) In-Reply-To: <20667.855188567@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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"