After installation, the configuration files for each module/service are available in the c-icap server configuration directory, /usr/local/c-icap/etc/ using the location folder specified in the 'configure' commands above. During the make install there will be some warnings about libtools, these can be ignored. After running the configuration script, we can build and install. Run the configure script, specifing where the server was installed, in both the with-c-icap and prefix arguments. Navigate to the modules folder (c-icap/c-icap-modules) and run the scripts to setup the Makefiles. The option is available to generate the documentation, if required. After running the configuration script, build and install the server. Run the configure script, specifying where the server should be installed, through the prefix argument. From where the repo was cloned to, navigate into the c-icap/c-icap folder and run the scripts to setup the Makefiles. The original baseline code has been cloned from the open source project. Sorry if these questions are a bit unspecific and basic, but just started with ICAP yesterday! ß Is there any - useful - way to accomplish this? Also, since I am super new to ICAP - are there any restrictions regarding which icap-server can be used?Like, is there any way to force requests to be handled with a metadefender-icap only, and not any other icap server? He wants me to try to have the requests/uploads sent to the c-icap server, but scanned with Windows Defender. Now the problem is, that my boss is basically a "Windows-only" person who says that any open-source AV can´t be trusted enough. So far it seems to work, at least EICAR files are detected. Now I managed to set up an icap-server using "c-icap" and tested it with "clamav". The files base64-encoded withing the upload method and this seems to lead to the fortigate not being able to scan it properly. I was tasked to set up an open-source icap-server to scan files that are uploaded in one of our web applications.
0 kommentar(er)
