Clam AV Native port X86

[GentleRV]

Very happy with a this port,a few bugs I like to report running all on a Windows 2003 server X64, but the native x64 app does not work with the message not a valid Win32 application 1) when running freshclam in a dos shell error can not create database\tmp directory 2) after creating the directories by hand running fresh clam can download some files but failed to download daily.cvd after 60 sec process is stopped.

[r1bnc]

@GentleRV Hey, have you tried compiling this repo? I tested the binary from the https://oss.netfarm.it/clamav/ and it works with the WinXP x86. If you tried to compile this repo, can you guide me on how to do it? What development environment did you use?

@sherpya What is the difference of this repo to the other https://github.com/clamwin/clamav? Is this being used for the clamwin project or is it the other? Can you add a documentation on how to do the port and compile the code in the repo? I am interested in porting clamav and possibly maintaing clamwin. But currently, I don't have the capability to use VS2019, I only use VS2012 now.

Also, what is the difference between the official clamav.net windows binary that can be found here https://www.clamav.net/downloads#collapseWin32 All I know is that version does not work on Windows XP and below.

Thank You

[GentleRV]

Hello,

I never tried to compile it as I also don't know how todo that. The x64 version give it is not a valid version and the win32 version does work but ends up with not downloading all the needed libraries to let ClamAV do his job. In the program a times is enabled to fetch the updated virus definition files, on my computer it failed to get the daily file within the set time limit of 60 Sec. I asked the developer to change this but got no response.

greetings

On Sun, 1 Nov 2020 at 18:57, gr01d notifications@github.com wrote:

@GentleRV https://github.com/GentleRV Hey, have you tried compiling this repo? I tested the binary from the https://oss.netfarm.it/clamav/ and it works with the WinXP x86. If you tried to compile this repo, can you guide me on how to do it? What development environment did you use?

@sherpya https://github.com/sherpya What is the difference of this repo to the other https://github.com/clamwin/clamav? Is this being used for the clamwin project or is it the other? Can you add a documentation on how to do the port and compile the code in the repo? I am interested in porting clamav and possibly maintaing clamwin. But currently, I don't have the capability to use VS2019, I only use VS2012 now.

Thank You

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/clamwin/clamav-win32/issues/7#issuecomment-720077025, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARW6N557DDLDUYBFPF5MD3SNVELXANCNFSM4QXISOYQ .

[r1bnc]

I think the developer may have abandoned the project, at some point in time I plan to continue his works. Porting clamav and maybe clamwin but for now, i don't have the hardware and ability to do that.

[sherpya]

my clamav is not abandoned, just lack of time to test/check/merge/fix/build, I've made 0.103.0, please test

[r1bnc]

Good to see you. :D Are we expecting ClamWin engine update soon? The clamwin forums have a lot of spam messages and I can only reach GuitarBob to talk to. Is Alch still around?

My previous message:

I would like to ask what is the difference of this: https://github.com/clamwin/clamav repository and this https://github.com/clamwin/clamav-win32/ repo? Can you add a documentation on what are the changes, and your development environment, and how to compile this repo? VS2019? mingw? Is this (https://github.com/clamwin/clamav) repo being used in the ClamWin project? or is it the clamav-win32 repo?

I may be interested in helping porting newer version of ClamAV, but currently I do not have the capability to use VS2019 or VS2017 (30GB disk space is too large for me, as I only have around 5 GB free space) and eventually help in maintaining ClamWin.

Also, what is the difference between the official clamav.net windows binary that can be found here https://www.clamav.net/downloads#collapseWin32 All I know is that version does not work on Windows XP and below and maybe the Unload virus from memory patch.

Thank you,

Please reply.

[sherpya]

ClamWin is a gui for clamscan/freshclam, with small change it could be adapted to the new engine, but the problem that is not easy to build, old python old wxWindows, Alch does not seem interested anymore

The difference with official port is compatibility, windows service, memory scan, scan progress, perhaps I've signed a CLA so they can also adopt my changes.

[r1bnc]

Thank you for replying. I know ClamWin, some of the links used in the readme on how to build it are unreachable, but I am also asking on what is the difference between the following repos: https://github.com/clamwin/clamav-win32 (The port for win32?) Referencing the repo below? https://github.com/clamwin/clamav (The patches?) Does this patched work with Linux too?

I am trying to understand the code, on what you added from the official clamav.net repo. Robert Scroggins said that you prepares the ports for Alch, but Alch seems unreachable according to Robert (http://forums.clamwin.com/viewtopic.php?t=4095). I would want to ask you on how you do the porting, some documentation may be helpful.

For how long are you planning to support earlier version of Windows? (win 98, Me, 2000) The user base of those appears to be decreasing or possibly non existent. I still know that a lot of users use Windows XP.

Thank You for your work in ClamWin and ClamAV ports

[midaspt]

Hi.

This isn't really an issue but more of a guidance/feature request.

I have been using a portable copy of ClamWin (coupled with ClamSentinel for easy tray access in Windows) for a very long time as a secondary on-demand virus checker.

Unfortunately, as you may be aware, ClamWin has stopped being updated nearly 3 years ago, but until recently, I could still get definitions updates alright via freshclam, so I kept using what I had in hope of finding a replacement solution.

After testing both the official ClamAV Windows binaries -- which I was unable to make work in my current setup -- and your native w32 builds, I was very favorably impressed by how similar it works to my now obsolete version.

From my point of view there's only one problem, as some paths appear to be hard-coded in absolute form.

E.g., when I run freshclam, database updates are always sent to a 'db' subfolder. Hence my request:

Can your builds include a way to point to relative paths? I'd appreciate it very much because it would provide a clear update path.

In case it helps understand my request, my 'ClamWin.conf' is posted to https://pastebin.com/k5ZNemar; my current 'freshclam.conf' is as follows:

DatabaseDirectory ..\db

DatabaseMirror database.clamav.net

UpdateLogFile ..\log\ClamUpdateLog.txt

LogVerbose yes

NotifyClamd .\ClamWin.conf

Foreground yes

I completely understand if you'd disregard this request, but I believe it would make your work more widely usable.