Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Installation Problem
Date:	Tue, 16 Aug 2005 17:03:54 +0100
MIME-Version:	1.0
In-Reply-To:	<loom.20050816T172238-574@post.gmane.org>
Message-ID:	<SERRANONOYOcIyz366p00000071@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Tom McKenna
>Sent: 16 August 2005 16:33

> Igor Pechtchanski <pechtcha <at> cs.nyu.edu> writes:
>> "cygcheck -cv cygwin" should show the actual files it thinks are missing
>> from the cygwin package.
> 
> This is strange - it says kill.exe is missing.  What is funny, if I
> create any file in any directory named kill.exe, it dissappears..  I
> think the server I am using might have been hacked or might be corrupted
> some how. 

  Check your anti-virus isn't responsible.  False positives have been known
to happen.  Some viruses and worms bundle a (legitimate) command-line tool
'kill.exe' which they use as part of their infection process; if your AV has
suddenly decided that anything called 'kill.exe' is malicious that might
account for the symptoms.

  And, yes, it would be an absolutely stupid and lousy piece of design if
your AV was triggering on just a filename rather than a hash or checksum or
signature of some kind.

  And yes, it has been known to happen.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -