full-disclosure - Just when you thought Macafee stuff was safe!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <001e01c3821b$b2ad1000$0100a8c0@p3600>
From: chows at ozemail.com.au (gregh)
Subject: Just when you thought Macafee stuff was safe!

----- Original Message ----- 
From: "Jeroen Massar" <jeroen@...ix.org>
To: "'gregh'" <chows@...mail.com.au>; <full-disclosure@...ts.netsys.com>
Sent: Wednesday, September 24, 2003 12:04 AM
Subject: RE: [Full-Disclosure] Just when you thought Macafee stuff was safe!

> -----BEGIN PGP SIGNED MESSAGE-----
>
> gregh wrote:
>
> > Try this one out for yourself.
> >
>
> <SNIP>
> > 8) Now imagine you have a network of around 20 or so users
> > (more, if you like) all with Macafee VSO and Spamkiller all going
through
>
> <SNIP>
>
> > 9) Now with Spamkiller AND Macafee VSO stopped, imagine what
> > work YOU will
> > have very shortly, fixing this.
>
> That's why there are virusscanners that check on inbound and
> outbound SMTP. Saving you from installing these tools on the
> client workstations and only having you to update one ;)
>

Ahh yes. I was annoyed so unclear. My apologies. The truth is that no matter
what you tell SOME users, they go do things for themselves anyway and spread
"the good news" to the point that you WILL find AV progs, anti spam progs
and so on installed on their windows machines anyway. Some of the users
believing this stuff are people in management positions, too. So, you either
do something and risk the results of that or deal with it the way it is. I
always choose the path of least conflict with people who pay me! Makes life
harder and all you can do is wait for the eventual stuffup so you can parade
in and say "You do remember me warning this will happen? Well let me fix it
but also let me CORRECT it" sorta thing.

The whole point, very long winded I admit, was to point out that Macafee VSO
and their Spamkiller conflict to the point of causing users to have to STOP
using one or the other, or both. In some real world cases this means that
things go downhill quickly. I guess all I can really say at this point is
that if you LOVE Macafee AV progs, don't use Spamkiller until they correct
this problem. I don't believe that VSO should be scanning Spamkiller stuff
"on the fly" but you cant stop it doing that right now.

Greg.