ECELeader

Thank you all for your help! The issue was solved after reinstalling all Firefox editions in my PC completely (removing the %AppData% folder as well) and reinstalling Firefox Developer Edition.

No I don't see ESET verification in the certificate when using Firefox Developer Edition: In the regular Firefox and Chrome it works just fine. Eset detects the other AMTSO tests (eicar, cloudcar etc). The only test failing is the anti-phising one. Interesting story! I know the importance of SSL filtering so I always keep it on.

Eset anti-phising and SSL filtering are not working in Firefox Developer Edition. They work fine in Chrome and regular Firefox, but not in the Developer edition. Using ESET SSP 12.2.29.0. Even tried pre-release channel to see if there is a fix.

Please note that multi-device-security will not activate a Smart Security Premium license but an Internet Security one. That means that you won't be able to use the Password Manager and Secure data encryption features.

Eset is using the term Macedonia in it's official sites and products, when referring to this country: https://en.wikipedia.org/wiki/North_Macedonia Please use the appropriate official name of the country North Macedonia, used under the national agreements. Using the name Macedonia without the official prefix North is insulting for Greeks and against the international agreements. The largest area of the region of Macedonia is part of Greece and only the most northerner area is part of the country of North Macedonia where it is officially named after. Please respect the official naming of the country and the international treaties and rename the country to its official name North Macedonia.

Well the thing is I don't want to block lxcore.sys and lxss.sys drivers because I actively use WSL on a daily basis. I want to use WSL while still be protected from threats like Bashware.

Thank you for your response! There is a new type of malware called Bashware that takes advantage of the WSL. See here and here. I have two important questions: 1) By excluding the folder of WSL app, is ESET still protecting from such type of attacks mentioned above? 2) Is ESET following Microsoft guidelines and instructions, specified in the Microsoft article regarding Pico Processes such as WSL? A reassurance by ESET development team would be great to know if ESET products are implementing and following the Microsoft standards mentioned in the article. If yes, since which version is the feature supported?

In a post in October there was this issue with High CPU usage and slowdown when using WSL in Windows. A temporary solution to this problem was to exclude the folder "%userprofile%\AppData\Local\Packages\DISTRO_APP_NAME" from Eset Realtime Protection. This solution is not ideal though because ESET doesn't protect processes run in WSL mode. I noticed that Microsoft has issued an article explaining how 3rd parties AVs and Firewalls like ESET should interact with WSL. Link: WSL Antivirus and Firewall Compatibility. Are ESET's developers aware of this? Are there any plans to implement this in a future version? I know a lot of people that use WSL mainly for development purposes and such a feature would be appreciated by the programming community that use ESET.

Have you tried as ESET to submit a Permissions Declaration Form for Google Play to review as stated here and here? Maybe Google can make an exception for ESET as anti theft SMS command is a core function of Anti-Theft.

Thanks for the apk link, but the version offered there is older than the Play Store version. Also, will it notify users to download new version when needed?

Please ESET provide an optional apk download from your site where the app has SMS text commands and other security features that Google forbids through play store policies.

Thanks for the info! It would be great to have this changelog posted here in forum for each update or displayed inside eset program in Help ans Support -> About section.

The score shows only the results of proactive detection (malware was successfully blocked by the test product, prior to execution). A product is considered to pass phase 1 if after running the python script manages to keep the system clean in the end (clean sheet). You can read about the test method here.

It would be great to have a detailed changelog for pre-release versions, so that people who choose the pre-release cycle, know what modules were added/changed in order to focus bug testing to those areas. For example, today I updated to 12.0.31.0 and I do not know what was added/improved.

Although The PC Security Channel [TPSC] is not an official AMTSO member, it is a worth noting channel that uses a consistent methodology to test security products. It is a respected chanell to IT, programmers and av-fans people. I starting using ESET products this year and bought 8 licenses in total and I am disappointed that ESET failed this test. As a programmer I also code in Python and I am worried by the failed test.