Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 10 Jan 2005 17:11:50 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygcrypt-0.dll infected Message-ID: <20050110221150.GA5006@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <41E2DCC4 DOT 1060506 AT watchmark DOT com> <20050110204419 DOT GL23702 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Mon, Jan 10, 2005 at 04:40:57PM -0500, Dick Repasky wrote: >Rather than telling users to bug the anti-virus company it might be worth >having someone from cygwin contact them to explain the issue. It might >also be worth doing a little bit of home work. That is, get a copy of the >malware, unpack it, and check to see whether cygcrypt-0.dll is included in >its entirety. What if it's really only something that bears the name and >that the anti-virus company is checking names only? > >Just my 2 cents, The fact that a company is inconveniencing its customers for no good reason should be a more than adequate goad for the company to fix its problem. I don't see any reason to set the precedent of having "someone from cygwin" do investigation when cygwin isn't doing anything wrong. If Trend Micro doesn't want to fix the problem then presumably people will take the next logical step. cgf -- 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/