Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!dkuug!freja.diku.dk!kimcm
From: kimcm@diku.dk (Kim Christian Madsen)
Newsgroups: comp.unix.shell
Subject: Re: Beware xargs security holes
Message-ID: <1990Oct31.233124.8208@diku.dk>
Date: 31 Oct 90 23:31:24 GMT
References: <1990Oct24.0100 <john.656921455@troch> <649@inews.intel.com> <653@inews.intel.com> <303@cadlab.sublink.ORG>
Organization: Department Of Computer Science, University Of Copenhagen
Lines: 14


Just my $0.02 to the ongoing discussion of:

	find .... | xargs rm

If you're really worried about *NASTY* users and embedded newlines in files,
why use xargs at the receiving end of find, and not just settle with:

	find .... -exec /bin/rm {} \;

Yes I know that it spawns a lot of processes compared to the xargs solution,
but it is also a secure way of removal of files with embedded newlines.

					Kim Chr. Madsen