Krzysztof.Wawro 0 Posted January 9, 2020 Posted January 9, 2020 Hi, I have a big problem. ESET Endpoint Security since several day change my general.config.filename value to eset_security_config_overlay.js (Mozilla Firefox about: config). When i Edit this file (add personal values) i am not resolving my problem because if i run mozilla firefox once again, the file rollback to default value. I attached screen from Mozilla Firefox about config. Mozilla Firefox version ESR 60.8 x86 Eset Endpoint Security 7.2.20.55.0 Please help me, how can i turn off this settings or how can i change content this file.
Administrators Marcos 5,468 Posted January 9, 2020 Administrators Posted January 9, 2020 You can disabling adding the root certificate to known browsers once it has been added as shown below:
Krzysztof.Wawro 0 Posted January 9, 2020 Author Posted January 9, 2020 Hi. Thank You very much. It is posible to delete this certificat via esmc ? Certificate still is default value on mozilla firefox.
Administrators Marcos 5,468 Posted January 9, 2020 Administrators Posted January 9, 2020 Any reason why you would you need to remove the root certificate? Disabling SSL filtering should do it but doing so will expose your computer at risk since SSL communication will not be scanned and possible malware on https websites may not be detected. My understanding was that you just wanted to prevent eset_security_config_overlay.js from being created.
Krzysztof.Wawro 0 Posted January 9, 2020 Author Posted January 9, 2020 yes, i want to prevent created eset_security_config_overlay.js on mozilla general.config value because i have personal *.js file. If i delete files eset_security_config_overlay.js from C:\Program File (x86)\Mozilla Firefox and C:\Program File (x86)\Mozilla Firefox\default\pref and turn off "add the root certyficate to known browser" i resolving my problem because in about:config (general.config.filename) i have value with my personal *.js file
Administrators Marcos 5,468 Posted January 9, 2020 Administrators Posted January 9, 2020 As I wrote, disabling the option to add the root certificate will solve the issue with creation of eset_security_config_overlay.js. However, you'll need to import the root certificate to the system trusted CA store and to Mozilla's trusted CA store manually or via a group policy or by some other means in order for SSL scanning to work.
Krzysztof.Wawro 0 Posted January 9, 2020 Author Posted January 9, 2020 yes, i understand. I do this. Now i need to delete eset_security_config_overlay.js from C:\Program File (x86)\Mozilla Firefox and C:\Program File (x86)\Mozilla Firefox\default\pref because these are still are default. It is possible to doing this via ESMC ?
Krzysztof.Wawro 0 Posted January 10, 2020 Author Posted January 10, 2020 Hi, Please tell me, what kind o features I lost after turn off "add the root certificate to known browser" ?
Administrators Marcos 5,468 Posted January 10, 2020 Administrators Posted January 10, 2020 Turning off that option without disabling SSL scanning would result in SSL communication issues since ESET's root certificate would not be trusted.
Administrators Marcos 5,468 Posted January 10, 2020 Administrators Posted January 10, 2020 As of Internet protection module 1385, you will be able to use custom config js files without issues even with the option to add the root certificate to known browsers enabled.
Krzysztof.Wawro 0 Posted January 13, 2020 Author Posted January 13, 2020 hi, Thanks. Currentlly I have Internet protection module 1381. When 1385 will be available ?
Administrators Marcos 5,468 Posted January 13, 2020 Administrators Posted January 13, 2020 8 hours ago, Krzysztof.Wawro said: hi, Thanks. Currentlly I have Internet protection module 1381. When 1385 will be available ? Should be available on the pre-release update channel soon.
Recommended Posts