Changelog version 11.1.216.0
Added: Option to disable Web Access Protection feature before product installation
Added: Support of Live Installer in ESET PROTECT
Added: Support of Amazon Linux 2023
Improved: On-Access scan improvement focused on responsivity and timeout elimination
Improved: Memory consumption of logging service
Improved: Option to define temp directory for ICAP
Fixed: Web Access Protection blocking localhost webpage
Fixed: Files downloaded from quarantine are in HTML format
Fixed: Excluded IP addresses in Web Access Protection not functional after pause and reset
Fixed: Other minor improvement and bugfixes
Option to disable Web Access Protection feature before product installation
In certain scenarios, our product may conflict with other software packages and their configurations on the system, primarily due to dependencies related to Web Access Protection (WAP) (e.g., iptables vs. nftables). To address these potential conflicts, we have introduced an option to disable the WAP feature before installing our product.
This option is implemented to provide flexibility and ensure compatibility with various system configurations. By allowing the WAP feature to be disabled, we aim to prevent installation issues and ensure a smoother setup process for customers who may encounter conflicts with existing software.
Installation
To install the product without the WAP feature, use the following environment variable during the installation process locally:
# example using sudo ESET_DISABLE_WAP=1 sudo -E ./efs.x86_64.bin
# example under root ESET_DISABLE_WAP=1 ./efs.x86_64.bin
When installing without WAP, the following dependencies should not be installed and should be removed if they are already present on the system before product installation:
ca-certificates
libnss3-tools (rhel nss-tools)
nftables
Warnings:
Permanent Disablement: Disabling the WAP feature during installation is a permanent action. Subsequent upgrades of the product will not re-enable WAP, even if the environment variable is not set during the upgrade process. The necessary WAP dependencies will be installed, but the feature itself will remain disabled.
Upgrade Process: To maintain the product without WAP, all upgrades must be performed with the ESET_DISABLE_WAP=1 environment variable. If you wish to enable WAP in the future, a new clean installation of the product is required.
Reactie toevoegen
Log in of registreer om een reactie te plaatsen.