Date: Wed, 2 Aug 2000 15:03:25 -0700 (PDT) From: Kris Kennaway <kris@hub.freebsd.org> To: "Chris D. Faulhaber" <jedgar@fxp.org> Cc: Brian Fundakowski Feldman <green@FreeBSD.org>, freebsd-audit@freebsd.org Subject: Re: fuzz usage (was: Re: cvs commit: ports/security/fuzz Makefile) Message-ID: <Pine.BSF.4.21.0008021502420.49766-100000@hub.freebsd.org> In-Reply-To: <Pine.BSF.4.21.0008021446400.25663-100000@earth.causticlabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0008021502420.49766-100000>