Show Advanced KnowledgeHide Advanced Knowledge

Revision Virus Scanner

1 Initial Problem

There is already a possibility to add a virus scanner to ILIAS. But this kind of implemtation doesn't check all file uploads. Due to different implementations of file uploads, the virus scanner can't check all files.


Another "problem" is, that you need an additional cron job to scan the data directory, but you can't handle the messages after the scan finished. If there are a lot of false positive detections, the scanner will send you a huge list of "infected" files.

2 Conceptual Summary

There are four points, a virus scanner should handle:

1. Check all file uploads. It should also check the Upload in the different moduls in ILIAS. This could be done with a File Upload Service preprocessor.
2. Should work with all command-line virus scanner. At the moment, you can choose between Sophos, AntiVir and CalmAV. But there are different implementations for this different software products.
3. It should check the files regularly by a cron job. Perhaps somebody uploads a virus in a file, and the Scanner doesn't know it yet.
4. The result of virus scanner cron job should be visible in ILIAS (a table with a filter and the possibility to take actions: ignore, delete, try to clean)

3 User Interface Modifications

3.1 List of Affected Views

There are no views affected. The Settings in Setup will be the same as now.

4 Technical Information

The implementation depends on

• HTTP-Service: https://github.com/ILIAS-eLearning/ILIAS/pull/466
• FileUpload-Service: File Upload Service

The Virus-Scanner will check all uploaded files which are handled by the File Upload Service.

5 Contact

• Author of the Request: Raimann, Marcel [raimann]
• Maintainer: Schmid, Fabian [fschmid]
• Implementation of the feature is done by: Schmid, Fabian [fschmid]

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• sr.solutions

7 Discussion

JourFixe, ILIAS [jourfixe], May 22, 2017: We highly appreciate this feature request and schedule it for 5.3

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.