c-icap | Glasswall modifications to the codebase

by filetrust C Version: Current License: LGPL-3.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | c-icap Summary

c-icap is a C library. c-icap has no bugs, it has a Weak Copyleft License and it has low support. However c-icap has 2 vulnerabilities. You can download it from GitHub.

A demonstration that the Glasswall Rebuild SDK can be used within an ICAP service to regenerate documents.

Support

Quality

Security

License

Reuse

Support

c-icap has a low active ecosystem.

It has 3 star(s) with 6 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 9 have been closed. On average issues are closed in 27 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of c-icap is current.

Quality

c-icap has no bugs reported.

Security

c-icap has 2 vulnerability issues reported (0 critical, 0 high, 2 medium, 0 low).

License

c-icap is licensed under the LGPL-3.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

c-icap releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of c-icap

Get all kandi verified functions for this library.

c-icap Key Features

No Key Features are available at this moment for c-icap.

c-icap Examples and Code Snippets

No Code Snippets are available at this moment for c-icap.

Community Discussions

Trending Discussions on c-icap

c-icap with Windows Defender

How to link to a shared library using Automake

QUESTION

c-icap with Windows Defender

Asked 2020-Aug-21 at 14:26

I was tasked to set up an open-source icap-server to scan files that are uploaded in one of our web applications.
The files base64-encoded withing the upload method and this seems to lead to the fortigate not being able to scan it properly.
Now I managed to set up an icap-server using "c-icap" and tested it with "clamav". So far it seems to work, at least EICAR files are detected. 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.
He wants me to try to have the requests/uploads sent to the c-icap server, but scanned with Windows Defender. ß 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?
Sorry if these questions are a bit unspecific and basic, but just started with ICAP yesterday!
Thank you!

...

ANSWER

Answered 2020-Aug-21 at 14:26

Check out this link: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/metadefender-icap-with-windows-defender-antivirus-world-class/ba-p/800234 to see what Microsoft offers regarding Defender+ICAP.

I have used commercial ICAP solutions in the past (like Bluecoat) that allow plugging in multiple commercial virus engines (Kaspersky, Sophos, ...). These are appliances, and you don't need to tell your boss their internals are probably some sort of Linux ;-)

You can probably also set up a commercial antivirus solution on your Linux system and use that. Looking at this link: https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-linux it may even be possible to run Microsoft's Defender on Linux. I haven't tried it myself though. Unlike your boss, Microsoft realizes software shouldn't be made to just run on Windows anymore (even MS-SQL Server now runs on Linux).

Source https://stackoverflow.com/questions/63483033

QUESTION

How to link to a shared library using Automake

Asked 2020-May-22 at 17:34

Having spent most of my development career in IDE I'm currently attempting to extend an Opensource project C-ICAP that uses Autoconf and Automake, so this may be a glaringly obvious answer to those more familiar with this toolset. I'm attempting to add a new service to the ICAP service that uses our proprietary shared library but can't work out the necessary updates to the Makefile.am to add our library to the link operation of the new service.

I need to create the equivalent of

...

ANSWER

Answered 2020-May-22 at 17:34

Since you're trying to add this to a shared object build, what you're looking for is libfoo_la_LIBADD = -lmylibrary. LIBADD as a global in Makefile.am is not supported.

Note that by default the link editor nowadays discards any library added to the linking line if they are not used to satisfy undefined symbols in the source objects. If you want to force linking to your library, you'd have to use libfoo_la_LIBADD = -Wl,--no-as-needed -lmylibrary -Wl,--as-needed, but that might complicate the build quite a bit.

Source https://stackoverflow.com/questions/61953958

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install c-icap

The original baseline code has been cloned from the open source project https://sourceforge.net/projects/c-icap/.
From where the repo was cloned to, navigate into the c-icap/c-icap folder and run the scripts to setup the Makefiles. Run the configure script, specifying where the server should be installed, through the prefix argument. After running the configuration script, build and install the server. The option is available to generate the documentation, if required.
Navigate to the modules folder (c-icap/c-icap-modules) and run the scripts to setup the Makefiles. Run the configure script, specifing where the server was installed, in both the with-c-icap and prefix arguments. After running the configuration script, we can build and install. During the make install there will be some warnings about libtools, these can be ignored. 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. For a module/service to be recognisd by the C-ICAP server its configuration file needs to be included into the main c-icap server configuration file. The following command adds the gw_test.conf file. Modules currently available for inclusion gw_test.conf or gw_rebuild.conf.
On the host server run the ICAP Server with the following command. From a separate command prompt, run the client utility to send an options request. The module specified in the -s argument must have been Included into the gw_test.conf file in the step above. Run the client utility sending a file through the ICAP Server. A full list of the command line options available to the client utility are available from the application's help option.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: