OPSWAT MetaDefender Core v4.17.1
Ab sofort steht die Lösung MetaDefender Core von OPSWAT in der Version v4.17.1 zur Verfügung
Programmname
Ab sofort steht der Anti-Malware Multiscanner MetaDefender Core von OPSWAT in der Version v4.17.1 zur Verfügung.
06.01.2020 => Releasedatum Hersteller
19.12.2019 => Releasedatum ProSoft
Lizenzinfo
Bei dieser Version handelt es sich um ein Minor Release und somit ist kein neuer Lizenzschlüssel notwendig.
Diese Version kann mit einem Lizenzkey v4 verwendet werden.
Bug Fixes
- Core could become unavailable to clients when under high load
Data communication channel between Core and Node service could be broken when under high load, some fixes and enhancement made to reduce this, and we keep working on this to optimize product operations.
- Processing giant files (> 50 GB) could be stuck at hash calculation
Hash calculation with pre-set timeout value (10 minutes) could be exceeded when processing giant files (> 50 GB) and then stuck at 5% forever. But now Core should be able to process ten times of that without any problem.
- Scan could be failed with "not available" result for File type analysis when under certain circumstances
- When handling archive files with empty folder(s) nested (fixed on this version).
- File type processing takes too long exceeding pre-set timeout and messed up with retry mechanism on Node (fixed on this version).
- Product resource manager has some inner issues while processing reference of object (issue found, working on a fix).
- Memory leak issue on Core process
Found and fixed all potential memory leak issues found via scheduled checks.
- Temporary files not cleaned up when archive extraction timed out
When archive extraction timed out, processing files extracted from archive could be leftover without cleaning up properly.
- Webhook continuous fixes and updates
- Redundant warning log messages populated even when not using webhook mode
- Core could be crashed itself when trying to close a not-found bath with callback
- Callback sent to client with wrong status when Core is restarted
- Visibility level smaller than full details might break batch result display
When setting visibility level smaller than "Full details" under workflow rule, batch_id could be missing leads to wrong batch details display on UI
- Minor UI fixes
- The field "File Password" on the file processing UI not cleared up after empty file selected
Neue Funktionen
- Deep CDR Engine configuration:
- Major experience improvement by adding all configuration options for each file type
- Ability to include the content of removed scripts (javascript, VBA Macros, etc.)
- Enhanced our Proactive-DLP engine support:
- Added support for IPv4 and CIDR detection
- Redaction can be defined based on detection certainty level
- Support Proactive DLP on Unix based systems
- Improved logging by exposing extraction errors for archives
- Improved support for large files (over 50GB)
- Improved logging and support for webhooks