Changelog

• Introduced internal changes.

• Resolved an issue that caused the time-out value to not be updated when Dr.Web Agent requested updates via Dr.Web Proxy Server, which could lead to loss of connection with Dr.Web Server.
• Resolved an issue that caused Dr.Web Proxy Server to stop responding when rotating large log files.

• Added Anti-scam—a feature that protects from phishing calls. Now you can limit the duration of calls from unknown and hidden numbers.
• Improved application stability.
• Internal changes.

• Introduced internal changes.

• Introduced internal changes.

• Introduced internal changes.

• Introduced internal changes.

• Added support for FreeBSD OS.
• Changed flag --drw to --drweb.
• Added flag --version for displaying the tool’s version.
• Changed filenames for the tool (fixit4u.amd64 > fixit4u-linux-amd64; fixit4u.arm64 > fixit4u-linux-arm64; fixit4u.i386 > fixit4u-linux-x86).
• Fixed issues and increased the performance of the tool.

You can now specify in the Control Center which actions are to be applied to different types of threats detected by the “Scanner” and “SpIDer Guard” components on stations running Android OS. The “Check for Adware” and “Check for Riskware” settings have been replaced with the action selection. If the checks for adware and riskware used to be disabled, the default action applied to such programs is set to “Ignore”; otherwise the default action for all threat types is “Report”.

• Updated anti-virus engine.
• Discontinued support for Android OS version 4.4. The minimum supported version is now 5.0.
• Added the ability to apply automatic actions for threat categories in SpIDer Guard and Scanner.
• Fixed an issue with endless screen refresh in the browser when the “Adult sites” category was enabled.
• Internal changes.