12. Release notes
MetaDefender Core v4.19.2Released on 07 Dec 2020 |
This is a release focused on bug fixes. |
New features / Behavior changes |
|
Non-persistent scan mode |
A stateless scanning solution to improve performance. When triggered, MetaDefender Core will not write any scan result into its database. Note: Webhook scanning fashion must be used from client side to retrieve scan result back from MetaDefender Core. Details: Using dbmode=3 setting described at 3.2.1. Startup Core Configuration |
Interactive engine removal on UI |
Any engine module could be removed on the management console (instead of using CLI tool). No service restart is required, no command to run. Details: 7.2.2. Modules (Remove engines) |
New Identity Provideres (IDP) supported and verified for Single Sign On (SSO) |
|
Data retention supported for statistics |
Data stored in statistics warehouse could be configured to clean up. Details: 3.5. Data retention |
Minor supports / changes |
|
Bug fixes |
|
Performance degradation issue mitigation |
|
Memory leak |
Both could happen on ometascan and ometascan-node processes under certain circumstances. |
Incompatible Nginx cipher algorithm |
Default acceptance cipher algorithm list modified to be less strict. |
Missing vulnerability detailed result |
Vulnerability detailed result could be missing from final scan report in some cases. |
Very high CPU continuous usuage occupied by node process |
Might happen when extraction failed and then affecting to the completion of hash calculation process, result in high CPU usuage continously. |
Potential service crash |
|
Issues with scan result report |
|
Proactive DLP setting issue with unicode characters |
The unicode setting value could be malformed after Core / Proactive DLP upgrade |
Other product functional issues |
|