Nasty propaganda by

Nasty propaganda by "security tool" providers

Secure Home | Search | About
 General Computer Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Nasty propaganda by "security tool" providers Volker Birk 08-05-2006
Posted by Sebastian Gottschalk on August 5, 2006, 6:29 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
B. Nice wrote:

>> So, it being detected means that he's got the right idea, about how the
>> actual malware works, but what he's failed to address is that his POC is
>> worthless on a properly configured computer.
>
> What do you mean by "properly configured computer"?

Please add at least a smilie when you know that he doesn't know an answer.

Anyway, even that has been discussed: Any security-related software
should, if it has to open windows, explicitly catch and ignore all
unknown messages. Microsoft could probably change DefaultWinProc(), but
it would be risky in terms of breaking applications. Nothing of this is
in your hand if you don't have the source code and didn't compile it
yourself, and I've never seen any software where this behaviour could be
optionally enabled by configuration.

Posted by Leythos on August 5, 2006, 7:10 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> B. Nice wrote:
>
> >> So, it being detected means that he's got the right idea, about how the
> >> actual malware works, but what he's failed to address is that his POC is
> >> worthless on a properly configured computer.
> >
> > What do you mean by "properly configured computer"?
>
> Please add at least a smilie when you know that he doesn't know an answer.
>
> Anyway, even that has been discussed: Any security-related software
> should, if it has to open windows, explicitly catch and ignore all
> unknown messages. Microsoft could probably change DefaultWinProc(), but
> it would be risky in terms of breaking applications. Nothing of this is
> in your hand if you don't have the source code and didn't compile it
> yourself, and I've never seen any software where this behaviour could be
> optionally enabled by configuration.

I'm waiting on you to explain how to configure a Windows computer so
that AV tools are completely unnecessary on a machine used by a typical
family with kids and adults for