From owner-freebsd-audit Wed Aug 2 15: 3:27 2000 Delivered-To: freebsd-audit@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id BC84237B6B3; Wed, 2 Aug 2000 15:03:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BA7592E819A; Wed, 2 Aug 2000 15:03:25 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 2 Aug 2000 15:03:25 -0700 (PDT) From: Kris Kennaway To: "Chris D. Faulhaber" Cc: Brian Fundakowski Feldman , freebsd-audit@freebsd.org Subject: Re: fuzz usage (was: Re: cvs commit: ports/security/fuzz Makefile) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Aug 2000, Chris D. Faulhaber wrote: > > I'm gonna see what bugs I can find with fuzz in the non-gnu stuff, of > > course starting with your suggestions, and I'll post any specifics to > > -audit. I encourage anyone else who's looking for some useful things > > to do to join -audit, too! > > > > Of course, beware of using fuzz on a machine with multiple users. Fuzz > creates temp files in /tmp using the tested program's name and run number > (e.g. make.9999, make.9998, etc). While it does clean up after itself, > the program does no sanity checking for links, etc, and will gladly > overwrite an existing file (or the other end of a sym link). In fact you should probably only ever run it in a jail in case you trash your machine :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message