public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michael A Chase" <mchase@ix.netcom.com>
To: <cygwin@cygwin.com>, "Randall R Schulz" <rrschulz@cris.com>
Subject: Re: anybody else also infected
Date: Wed, 13 Feb 2002 21:02:00 -0000	[thread overview]
Message-ID: <019901c1b514$b18c7470$9b00a8c0@mchasecompaq> (raw)
In-Reply-To: <5.1.0.14.2.20020213201502.00aa4258@pop3.cris.com>

----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>
To: "Michael A Chase" <mchase@ix.netcom.com>; <cygwin@cygwin.com>
Sent: Wednesday, February 13, 2002 20:18
Subject: Re: anybody else also infected


> My NAV does not detect any virus in /bin/cygz.dll from the 1.1.3-6 package
> archive in my download directory.
>
> Any idea why? When was the last time you updated your NAV virus
> descriptions? I updated mine this AM.
>
> At 19:27 2002-02-13, you wrote:
> >Update to zlib-1.1.3-7.  NAV thinks it detects the virus in the 1.1.3-6
> >version of the file, but not in the 1.1.3-7 version.
> >
> >Since you reported the false positive to SARC, the next release of the
NAV
> >data files may have it fixed as well.

I ran LiveUpdate manually just before the last time I tested the files.  I
scanned the files both in the archive and after extracting.  The cygz.dll in
1.1.3-6 is tagged, the copy in 1.1.3.7 isn't.

WinXP Pro 5.1 Build 2600
Virus definitions: 2002/02/13 (2002/02/11 before LiveUpdate)
Norton SystemWorks: 5.0.1 aka 2002.05 Build 59
NAV: 8.00.58B

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-02-14  5:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 18:05 hongxun lee
2002-02-13 18:17 ` Randall R Schulz
2002-02-13 18:23   ` hongxun lee
2002-02-13 19:28     ` Michael A Chase
2002-02-13 20:18       ` Randall R Schulz
2002-02-13 21:02         ` Michael A Chase [this message]
     [not found] <01A7DAF31F93D511AEE300D0B706ED92019ECD65@axcs13.cos.agilent.com>
2002-02-14  5:29 ` hongxun lee
2002-02-14  6:24   ` Larry Hall (RFK Partners, Inc)
2002-02-14  6:35     ` Peter Buckley
2002-02-14  7:02       ` Larry Hall (RFK Partners, Inc)
2002-02-14  7:13         ` Peter Buckley
2002-02-14  7:19           ` Larry Hall (RFK Partners, Inc)
2002-02-14  7:31           ` David Starks-Browning
2002-02-14  7:37             ` Christopher Faylor
2002-02-14  7:58               ` Larry Hall (RFK Partners, Inc)
2002-02-14  8:36                 ` Christopher Faylor
2002-02-14 23:22                   ` Gary R. Van Sickle
2002-02-14  7:47             ` Larry Hall (RFK Partners, Inc)
2002-02-14  7:37       ` Christopher Faylor
2002-02-14 12:38 Jerry Boonstra

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='019901c1b514$b18c7470$9b00a8c0@mchasecompaq' \
    --to=mchase@ix.netcom.com \
    --cc=cygwin@cygwin.com \
    --cc=rrschulz@cris.com \
    /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).