well, avast could avoid scanning them. and then avoid marking them as viorus and throwing them into the chest.
Not virus ...... Suspicious
Anyway this is the price we pay for using generic/heuristic detections to be able to catch new virus before signature is created
If lots of undetected malware slipped by ..... what would you say then?
It treats 'suspicious' and 'virus' the same way though Pondus. In the bin and scare the user.
Don't get me wrong though, I agree that locking down threats at the earliest possible opportunity is good for everybody, and if my code unintentionally and inadvertently did bad things, it's right to lock it up. No questions. The problem is most developers aren't all major organisations that have the resources behind them to do such things as get a full security audit or buy expensive certificates that need renewing. etc. Avast! whilst being a market leader and doing a great job at fighting 'bad stuff' is slowly destroying hobbyist and the smaller developer, without putting anything back into it.
If Avast! wants to take a tough stand against 'baddies', that's good, but they should also have the same enthusiasm to ensure 'good' programs/programmers are recognised. Remember this is not auto-whitelisting that i am proposing. But a cheaper intermediate than buying thawte or other certification, that is just used for a specific MD5.
I can get a free class 1 ssl certificate by answering some questions here:
https://www.startssl.com/?app=32 and I envisioned something similar from Avast! for developers/users.
To answer the next comment on the next page about "what if the malware developers get a token. What then?" <-- That's exactly the same as them getting their worked signed by any other authority. s
What-if's such as that would prevent everything that ever progressed. And Avast! would not exist, nor would any other technology whatsoever. We'd still be freezing our butts off in caves because "'What if' the fire we created from rubbing sticks together burned us?"
