From: Chris Faylor <cgf@cygnus.com>
To: "Powell, Walt - TOP" <wlpowelljr@bpa.gov>
Cc: "'insight@sourceware.cygnus.com'" <insight@sourceware.cygnus.com>,
"Dorning, Kevin E - KGI-2" <kedorning@bpa.gov>,
"Liu, Tsu-huei- TOP" <thliu@bpa.gov>
Subject: Re: Win32.FunTime.d virus in cygwin1.dll
Date: Tue, 11 Apr 2000 09:53:00 -0000 [thread overview]
Message-ID: <20000411125332.A1789@cygnus.com> (raw)
In-Reply-To: <C1C8F90DEE8ED211BD4B0000F8FA5DE9BA6BE2@exch05.wins.bpa.gov>
On Tue, Apr 11, 2000 at 09:38:04AM -0700, Powell, Walt - TOP wrote:
>Our sysop has informed me that the file cygwin1.dll contains a virus called
>the Win32.FunTime.d.
>
>I obtained this file from the gzipped file egcs-1.1.1-cygb20.tar.gz,
>obtained from an earlier cygwin download. As far as I can tell, cygwin1.dll
>has not been altered at my site, and if this is true, the virus must have
>originated at the cygnus site.
>
>I am deeply concerned about this possibility. Can you provide any
>information or a secure version of cygwin1.dll?
I am not sure why you are sending email to the insight mailing list concerning
a DLL that you extracted from an EGCS tar file downloaded from a non-cygnus
web site.
However, we receive false alarms about this on a regular basis. There is
one virus-checking package which returns a fals positive on the Cygwin DLL.
That is not to say that it is impossible that your DLL is infected. I
would try testing it with multiple virus checking packages. If they all agree
then you probably do have an infected DLL. You can find a new DLL to download
at http://sourceware.cygnus.com/cygwin/ .
Christopher Faylor
Cygwin Engineering Manager
Cygnus Solutions, a Red Hat company
prev parent reply other threads:[~2000-04-11 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 9:35 Powell, Walt - TOP
2000-04-11 9:53 ` Chris Faylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000411125332.A1789@cygnus.com \
--to=cgf@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=kedorning@bpa.gov \
--cc=thliu@bpa.gov \
--cc=wlpowelljr@bpa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).