From: dian_cecht@zoho.com
To: Leo Famulari <leo@famulari.name>
Cc: 25278-done@debbugs.gnu.org
Subject: bug#25278: Acknowledgement (Possible virus found in icecat-45.5.1)
Date: Mon, 26 Dec 2016 17:41:36 -0800 [thread overview]
Message-ID: <20161227014136.GA21067@khaalida> (raw)
In-Reply-To: <20161227012415.GA14310@jasmine>
On Mon, Dec 26, 2016 at 08:24:15PM -0500, Leo Famulari wrote:
> On Mon, Dec 26, 2016 at 04:20:47PM -0800, dian_cecht@zoho.com wrote:
> > On Mon, Dec 26, 2016 at 06:57:50PM -0500, Leo Famulari wrote:
> > > On Mon, Dec 26, 2016 at 12:11:13PM -0800, dian_cecht@zoho.com wrote:
> > > > I just wanted to add that I went ahead and ran icecat-45.5.1 then rescanned
> > > > ~/.mozilla and nothing related to the virus popped up with the scan.
> > >
> > > Are the files with the same SHA1 hashes still present?
> >
> > So I rechecked the files listed in this bugreport and yes, the checksums are the
> > same. However, they no longer list as viruses according to ClamAV. I checked my
> > logs and I'm assuming that a database update fixed a false positive (freshclam
> > updates the database every 2 hours on my machine, and, afaik, the virus
> > definition was added in the last day or two).
> >
> > So it looks to me like it was simply a false positive.
>
> Good news!
>
> You can close the bug by sending a message to
> <25278-done@debbugs.gnu.org>.
Good to know. Thanks.
next prev parent reply other threads:[~2016-12-27 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 19:18 bug#25278: Possible virus found in icecat-45.5.1 dian_cecht
[not found] ` <handler.25278.B.148277993421450.ack@debbugs.gnu.org>
2016-12-26 20:11 ` bug#25278: Acknowledgement (Possible virus found in icecat-45.5.1) dian_cecht
2016-12-26 22:05 ` ng0
2016-12-26 23:57 ` Leo Famulari
2016-12-27 0:20 ` dian_cecht
[not found] ` <20161227012415.GA14310@jasmine>
2016-12-27 1:41 ` dian_cecht [this message]
2017-01-03 20:16 ` bug#25278: Possible virus found in icecat-45.5.1 David Craven
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161227014136.GA21067@khaalida \
--to=dian_cecht@zoho.com \
--cc=25278-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).