rmuch / clamav.managed Goto Github PK

There are a few new scan options in clamav.h that need to be added to the ScanOptions enum, as well as a new clcb_virus_found callback

Commit history can be found on the ClamAV GitHub repository.

I will use ClamAV.Managed.Samples.Gui is a startup project and is linked with libclamav + its db. when I run this sample it will crash the program at clamengine.cs line 292 having method 'ScanFile'. I have spent more than 3 days and couldn't get the solution. I have attached the screenshots of errors that show at console/output, runtime crash as well the line of clamengine.cs line 292. One more thing is ClamAV.Managed can scan files whose content is up to less than equal to (=<5 ).
ClamAV-Managed.pdf

Documentation files should be created for the ClamAV.Managed PowerShell cmdlets. PowerShell uses an XML format for cmdlet help, described in the links below:

• Creating Cmdlet Help - MSDN PowerShell Blog
• Writing Help for Windows PowerShell Modules - MSDN
• Writing Help for Windows PowerShell Cmdlets - MSDN

When the library is mature enough, align with ClamAV versioning.

Create NuGet package definitions.

I want to write a scheduler for this code. Could you please guide me

As per the lifecycle documentation:

.NET Framework 4.5.2, 4.6, and 4.61 will retire on April 26, 2022. These specific releases were previously digitally signed using Secure Hash Algorithm (SHA-1) certificates. This algorithm is no longer deemed secure. Go here to learn more about this retirement. Customers are encouraged to move to SHA-2. Go here to learn about validating your application functionality on the newer runtime version.

Release 0.4.0.0 will be upgraded to .NET Framework 4.8, as the last release exclusively supporting .NET 4.x.

.NET Framework 4.8: Support for .NET 4.8 follows the Lifecycle Policy of the parent OS. It is supported as a Windows component on the latest required update for the operating systems below. We recommend customers upgrade to .NET Framework 4.8 to receive the highest level of performance, reliability, and security.

Implement asynchronous file and directory scanning.

Asynchronous scanning using the async/await pattern new in .NET 4.5 would probably be the easiest to implement. However, this would require upgrading the solution projects to .NET 4.5, which might be a problem for those who wish to target earlier framework versions.

A good first step would be to provide asynchronous methods using the older Begin/End asynchronous programming model.

Numerous issues when trying to use ClamAV.Managed with the official build(s) of libclamav available at http://sourceforge.net/projects/clamav/files/clamav/win32/. Experienced with 0.98.3.

When hosting the win32 (32-bit) build of libclamav, cl_load will always return CL_EMEM.

Attempting to host the 64-bit build results in a BadImageFormatException.

Needs further investigation.

What does it mean that CLAMAV is working in Real time Mode?

.NET Core supports P/Invoke, so, in theory, everything should work fine. It should be tested and .NET Core-compatible builds should be ensured before .NET Core can be added to the compatibility matrix.

Currently, the plan is to use WiX to provide a Windows Installer package with the ability to select libraries, source code, documentation and PowerShell integration, primarily to facilitate automated deployment on servers.

As well as the WiX package, there will definitely be binary builds distributed in a ZIP archive.

ClamAV.Managed could also be distributed via NuGet, but the issue of how to provide ClamAV binary builds along with the managed libraries, especially to support Mac OS X and Linux, should be considered.

A ZIP archive distribution should be available for 0.2, and a Windows Installer package at a later version.

Upgrade ClamAV.Managed and ClamAV.Managed.Async to .NET Standard 2.0 the SDK-style (.NET Core) project format.

This could possibly be accomplished using automated tooling.

This may also necessitate upgrading other dependent projects to at least .NET 4.6.1, because earlier versions are not supported by .NET Standard, as per the documentation here.

Since the original issue (#8) was created, the .NET ecosystem has come a long way. This issue supersedes the previous one.

This will not be merged until after the 0.4.0.0 release, which will be the final release using the legacy .NET Framework.

libclamav has callbacks when a virus is found or when signatures are loaded. These could be exposed as events in ClamEngine.