"Mayayana" news Mon, 14 May 2018 13:27:27 GMT in alt.windows7.general, wrote:

"FredW" wrote

| According to you Malwarebytes is to blame for a false positive
| but at the same time you want to keep it a secret to Malwarebytes
| that they made a false positive and why they made a false
| positive. That does not make much sense to me, do you really
| expect Malwarebytes to correct false positives when you do not
| want to tell anything?
|

The whole job of MB is to distinguish malware
and warn about it. Since MB is prone to melodrama
and false positives it's not a safe product to use for
most people. Why MB attracts such a zealous fan
base is a mystery to me. Just because you love MB
that doesn't grant them some kind of authority.

Nor does it grant him permission to make up stories about my trying
to keep what needs to be done to fix it a secret. I *never* tried any
such thing, and, infact, wrote on more than one occasion in this very
thread what needs to be done to have this issue properly corrected.

False positives are becoming a widespread problem.
Partly because the methods to identify malware are
faulty and partly because security software companies
risk their reputation less from false positives than
from not catching real malware. So they increasingly
err on the side of caution.

There identification and research methods are unlike anything I've
experienced or known beforehand. And, the result, sadly, is a slew of
false positives. Malwarebytes is the ONLY company I know of,
seriously, that has people with no programming background or
knowledge play the role of malware researcher.

I would never recommend MB to anyone because
most of the people I know don't know enough to
assess MB's cries of wolf to decide whether one of
them is valid. Very few people do. My own experience
with MB showed it to be a dangerous program that
could easily do damage if allowed to make its own
decisions.

I stopped recommending MBAM several years ago when I had to clean up
a huge mess they made for me on a clients machine due to another
false positive. It took me hours to fix it. And when I was finished,
MB was removed from ALL of those machines. It'll never be reinstalled
on them so long as they're my clients.

I've run into similar false positives with my own
software from Avira. Someone wrote to tell me about
it. Otherwise I would have had no idea. My attempt to
contact Avira resulted only in robo-responses. No one
was minding the store. But even if they were responsive,
why is it my job to make sure all security software
recognizes my software? Should I buy and/or install
all AV products on a test machine and run every
compile past them? That would be absurd.

I had the same problem with BugHunter when I initially released it.
Although I did identify the false hit they were getting, I opted to
have them remove it properly vs me moving things around in my source
code to evade it. It took about a month or so before it showed as
clean.



--
To prevent yourself from being a victim of cyber
stalking, it's highly recommended you visit he
https://tekrider.net/pages/david-brooks-stalker.php
================================================== =
Plasma is another matter.