Reply to thread

Message

<blockquote data-quote="Emsisoft" data-source="post: 1014589" data-attributes="member: 10447">Thanks for reviewing our software! That&#039;s one of those moments when hell breaks loose in our development and QA teams because such anti-phishing results are totally unacceptable, not just for our customers but also for our own ambitions to provide highest quality protection.So we immediately did a thorough analysis of our code and verified all steps and components that are at play here, to trace down the source of the detection problem. Ultimately, we located a serious logic problem that appears when using the Emsisoft Browser Security extension in combination with a certain policy setting in Emsisoft Anti-Malware. To be more specific, functionality was broken when none of the Content Filtering options were enabled.We immediately released a hotfix update within a day that resolves the problem and improved our QA procedures to ensure that won&#039;t happen again. We would appreciate a re-test to confirm that it&#039;s fixed.Thank you so much for pointing us to this issue and apologies to all affected users of the software!</blockquote>

[QUOTE="Emsisoft, post: 1014589, member: 10447"] Thanks for reviewing our software! That's one of those moments when hell breaks loose in our development and QA teams because such anti-phishing results are totally unacceptable, not just for our customers but also for our own ambitions to provide highest quality protection. So we immediately did a thorough analysis of our code and verified all steps and components that are at play here, to trace down the source of the detection problem. Ultimately, we located a serious logic problem that appears when using the Emsisoft Browser Security extension in combination with a certain policy setting in Emsisoft Anti-Malware. To be more specific, functionality was broken when none of the Content Filtering options were enabled. We immediately released a hotfix update within a day that resolves the problem and improved our QA procedures to ensure that won't happen again. We would appreciate a re-test to confirm that it's fixed. Thank you so much for pointing us to this issue and apologies to all affected users of the software! [/QUOTE]

Verification