For example, for ClamD you may now specify MaxScanSize 10G in nf. Introduced the ability to suffix the MaxScanSize and other config file size options with a "G" or "g" for the number of gigabytes. Raised the MaxScanSize limit so the total amount of data scanned when scanning a file or archive may exceed 4 gigabytes. If you want a different update interval you can edit the timer unit file: sudo systemctl edit clamav-freshclam-once.timer Sudo systemctl status clamav-freshclam-once.timer The timer can be activated, audited, and the logs inspected: sudo systemctl enable -now clamav-freshclam-once.timer This takes the "burden of timing the updates" from Freshclam and puts it onto SystemD. Introduced a SystemD timer for running Freshclam updates, without sending Freshclam into the background. Alternatively, you can customize the cache size for ClamD by setting CacheSize in nf. The cache size option for clamd and clamscan is -cache-size. The cache size value should be a square number or will be rounded up to the nearest square number. Increasing the size of the clean file cache may improve scan performance but will require more RAM. Specifically, this version adds support for the Beginning Extended Area Descriptor (BEA01) type of UDF files.Īdded an option to customize the size of ClamAV's clean file cache. Please help us validate this release by providing feedback via the ClamAV mailing list or on our Discord.ĬlamAV 1.2.0 includes the following improvements and changes: Major changesĪdded support for extracting Universal Disk Format (UDF) partitions. Please take this time to evaluate ClamAV 1.2.0. The release candidate phase is expected to last two to three weeks before we publish the stable release or a second release candidate. But if you download the ZIP or TAR.GZ generated by GitHub, located at the very bottom, then an internet connection will be required during the build to download additional Rust dependencies.įor Docker users, there is no specific Docker tag for the release candidate, but you can use the clamav:unstable or clamav:unstable_base tags. All dependencies are included in this package. Tip: If you are downloading the source from the GitHub release page, the package labeled "clamav-1.2." does not require an internet connection to build. You may find the source code and installers for this release on t he /downloads page or t he ClamAV GitHub release page. Thanks.We are excited to announce the ClamAV 1.2.0 release candidate. Do I need this executable? VMware Tools is already working fine on my system should I just throw away this file? Or is there someplace online where I can download a newer version of VMwareToolsUpgrader.exe to replace this with? (I'm stuck using Fusion version 3.14 because I still run Snow Leopard, but I'm guessing that a newer version of VMwareToolsUpgrader.exe would still work.)Īny insight into this issue would be much appreciated. My guess is that it's a false positive, that the. I did so, and all the other anti-virus programs there said the file is OK only ClamXav still thought it's infected. I asked the moderator on the ClamXav forum whether he thought this is a real infection or a false positive, and he didn't know, but suggested I upload the file to and let them check it. I don't recall ever explicitly using this program, but perhaps Fusion uses it in the background I don't know.Īnyway, ClamXav claims that VMwareToolsUpgrader.exe is infected with something called -1302. The file (I guess it's a Windows program) has a creation and modification date of April 12, 2014. The file, which is in the VMware Fusion Application Support folder, tools-upgraders subfolder, is called VMwareToolsUpgrader.exe. I ran a scan with a Mac anti-virus program called ClamXav, and it flagged a file on my Mac as "infected".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |