X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4D90CD5E.7040808@bopp.net> Date: Mon, 28 Mar 2011 13:03:10 -0500 From: Jeremy Bopp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: EXTERNAL: Virus that deletes everything under c:/cygwin? References: <468547 DOT 38757 DOT qm AT web52801 DOT mail DOT re2 DOT yahoo DOT com> In-Reply-To: <468547.38757.qm@web52801.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 3/28/2011 12:07, Dante Allegria wrote: > --- On Mon, 3/28/11, Damon Register wrote: > >> this at a company. Is that so? Do you have an >> aggressive IS department who might have decided they don't like Cygwin? > > No, turns out it was because someone committed this into the nightly build scripts: > rm -rf $(DOES_NOT_EXIST)/* > > Should cygwin's rm have some built-in safeguards for this? :) Probably the only way to get this protection would be to remove the ability of the user running your build automation to delete the Cygwin installation in the first place. Otherwise, this could just as easily happen somewhere else such as a Perl script that doesn't even use rm. Depending on your situation, that may be easier said than done unfortunately. -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple