problem
For non-developers it is almost impossible to set up the freshclam.conf file, we don't even know it is necessary. don't know what settings to use, and certainly wouldn't know to run 'freshclam' in a terminal to pull the database. This is the sort of post-install thing that should be handled in the GUI.
Proposed solution
Please add the ability to input the text for the freshclam.conf file via the GUI. And give standard default examples per OS. Upon pressing 'OK' this would create the file in the clamav install folder, and then open the terminal as admin and run the 'freshclam' command.
Alternative solutions
AI just created a .BAT file that can run and automate this whole setup process, and it contains the defaults. Including that file in the install of the GUI could work. You could either launch it from within the GUI, or if that's problematic you could just give instructions for the person to find it in the install folder, right click, run as admin.
Additional context
I believe that safe open source applications like clamav should not be only for developers, but should be easily used by non-developers. ClamAV provide a 'one click' .msi installer for Windows and this is a great start. The total invisibility of the set up needed after that is a problem. You can solve that for them.
problem
For non-developers it is almost impossible to set up the freshclam.conf file, we don't even know it is necessary. don't know what settings to use, and certainly wouldn't know to run 'freshclam' in a terminal to pull the database. This is the sort of post-install thing that should be handled in the GUI.
Proposed solution
Please add the ability to input the text for the freshclam.conf file via the GUI. And give standard default examples per OS. Upon pressing 'OK' this would create the file in the clamav install folder, and then open the terminal as admin and run the 'freshclam' command.
Alternative solutions
AI just created a .BAT file that can run and automate this whole setup process, and it contains the defaults. Including that file in the install of the GUI could work. You could either launch it from within the GUI, or if that's problematic you could just give instructions for the person to find it in the install folder, right click, run as admin.
Additional context
I believe that safe open source applications like clamav should not be only for developers, but should be easily used by non-developers. ClamAV provide a 'one click' .msi installer for Windows and this is a great start. The total invisibility of the set up needed after that is a problem. You can solve that for them.