From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which desktop antivirus?
Date: Sun, 30 Oct 2011 12:50:49 +0000 [thread overview]
Message-ID: <201110301250.51263.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201110291940.52957.michaelkintzios@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1536 bytes --]
On Saturday 29 Oct 2011 19:40:49 Mick wrote:
> On Saturday 29 Oct 2011 19:25:00 Pandu Poluan wrote:
> > On Oct 30, 2011 1:15 AM, "Mick" <michaelkintzios@gmail.com> wrote:
> > > pagefile.sys of a WinXP OS and it thinks it is a Win32:Patched-HO.
> >
> > If pagefile.sys is detected as a malware, most likely the actual malware
> > was once loaded into (Windows XP's) memory got swapped, and avast! picked
> > up its remnant. Loaded into memory doesn't mean that the malware was
> > active, if the Windows XP was equipped with a good antivirus.
>
> Interesting! The WinXP has Microsoft Security Essentials on it. I'll ask
> my wife if it picked up anything lately.
She can't recall any MSE reports of malware. I did check the WinXP fs for all
the files and registry entries that this trojan is meant to create and none
were present. Then I've zero'ed the pagefile and a second scan did not flag
anything up.
I also checked for a reported trojan in a Windows 7 vdi file (in virtualbox).
Nothing found there either. I am tempted to think that avast! is rather
super-sensitive. However, avast! also picked up some php files from a backed
up website - so this may be a worthwhile find.
Anyway, I can't make it integrate with kmail which was the original user
requirement. Tried this script but the kmail Antivirus Wizard will not pick
it up:
http://forum.avast.com/index.php?topic=17898.0
So I am now heading for clamav to see how that works with a Linux desktop.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-30 12:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 11:27 [gentoo-user] Which desktop antivirus? Mick
2011-10-22 11:29 ` Nilesh Govindarajan
2011-10-22 11:43 ` Florian Philipp
2011-10-22 14:22 ` Jonas de Buhr
2011-10-22 15:40 ` Mick
2011-10-22 17:03 ` [gentoo-user] " Nikos Chantziaras
2011-10-22 20:31 ` Neil Bothwick
2011-10-30 12:35 ` Mick
2011-10-22 11:37 ` Nikos Chantziaras
2011-10-22 14:07 ` Adam Carter
2011-10-22 14:22 ` Pandu Poluan
2011-10-22 15:14 ` Nikos Chantziaras
2011-10-22 19:55 ` Mark Knecht
2011-10-22 20:47 ` Florian Philipp
2011-10-22 21:30 ` Volker Armin Hemmann
2011-10-23 4:04 ` Adam Carter
2011-10-23 7:49 ` Mick
2011-10-23 9:06 ` Florian Philipp
2011-10-22 17:27 ` [gentoo-user] " Dale
2011-10-22 18:46 ` Mick
2011-10-22 19:15 ` Dale
2011-10-23 11:01 ` Volker Armin Hemmann
2011-10-29 15:39 ` Mick
2011-10-29 17:26 ` Mark Knecht
2011-10-29 18:11 ` Mick
2011-10-29 18:25 ` Pandu Poluan
2011-10-29 18:40 ` Mick
2011-10-30 12:50 ` Mick [this message]
2011-10-30 13:32 ` James Broadhead
2011-10-30 15:29 ` Mick
2011-10-31 9:54 ` James Broadhead
2011-10-30 20:01 ` James Broadhead
2011-10-23 22:47 ` Dale
2011-10-22 19:05 ` Andrey Moshbear
2011-10-22 19:17 ` Pandu Poluan
2011-10-23 7:20 ` du yang
2011-10-23 8:38 ` Pandu Poluan
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=201110301250.51263.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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