Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: From: Mike Little To: cygwin AT sourceware DOT cygnus DOT com Subject: RE: cygwin-net: viruses in .tar.gz files?? Date: Thu, 8 Jun 2000 12:18:42 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-8859-1" > -----Original Message----- > From: Colman Curtin [mailto:colman DOT curtin AT trintech DOT com] > Sent: Thursday, June 08, 2000 12:00 PM > To: cygwin AT sourceware DOT cygnus DOT com > Subject: RE: cygwin-net: viruses in .tar.gz files?? > > > >I downloaded setup.exe for the latest cygwin release from > >sourceware.cygnus.com. I run it and select a US mirror. I > tried both > >ftp.freesoftware.com and sourceware.cygnus.com. > > > >When it downloads the gcc tarball my VirusScanner detects a virus in > >it. I'm running McAffee 4.5.0 (virus definition 4.0.4080). It > >doesn't name the virus, and can't clean it. To be safe I just quit > >setup. > > > >Has anyone else seen this? > Turn off scanning of compressed files McAffee seems to get a > bit upset when > fed a .tar.gz file - It crashes on my machine but subsequent > scanning of the > install shows all is clear. > -Coley. This has been my experience too, as I replied to someone yesterday, the only way I could initially install was by disabling the virus scanner. Mine is version 4.0.3a, (virus definition 4.0.4081, scan engine 4.0.02). Of course scanning setup.exe before running it, and scanning everything afterwards showed no problems. It does seem to point to the handling of .tar.gz files. As a further clue, I have installed several updates since the first time, none of which required me to turn off the scanner, but none of which were installed over the internet. That is I have always, d/loaded the tarball first. It may be the virus scanner is trying to read ahead in the tarballs before they have finished d/loading, and that is what gives it problems. Hope this helps, -- Mike Little Share what you know. Learn what you don't. ServicePOWER Business Solutions Ltd home: mike AT ampersoft DOT co DOT uk -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com