Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Mittels Scroll Versions veröffentlicht aus dem Bereich CSMB und Version 4.4.0.

Button to
SpaceDefaultLink[destination=Optional[PageResourceIdentifier[spaceKey=CSH,title=Vorverarbeitung]],body=Optional.empty,tooltip=Optional.empty,anchor=Optional.empty,target=Optional.empty]
TitleDeutsch



About Pre-Processing

Every file that is being transferred to the Cryptshare server can be checked by a pre-process command. This provides the possibility to check files for viruses before encrypting them.
If a check finishes with a 'positive' exit code (i.e. a virus has been found) the file will be removed from the transfer.

Virus check

Using ClamAV

Our Virtual Appliance and Hardware Appliance systems are delivered with a preinstalled ClamAV virus scanner.

Note

Please note that the ClamAV virus scanner cannot scan files larger than 2 GB. This technical limitation applies only to individual files, not to the total size of the transfer. For example, a transfer with 10 files of 300 MB each can be checked, but not a transfer containing a single file of 3 GB.

For performance reasons, the default configuration of ClamAV is set to only scan files up to 25M files.


If you also want to check larger files (up to 2GB), change the MaxScanSize and MaxFileSize parameters in the /etc/clamd.conf file and restart the ClamAV service with the rcclamd restart command.

Please refer to the Pre-Processing Limit section to define how Cryptshare should process files that are larger than the processing limit of your virus scanner.

Using other virus scanners

For self-installed systems it is necessary to integrate a separate virus scanner into the pre-processing. Please use the required command line for the pre-processing, which you can get from the manufacturer of your virus scanner.

Please check the manufacturer's documentation to determine the maximum file size the scan can process. Most virus scanners have a technical limit with a file size of 2 GB. This limitation applies only to individual files, not to the overall size of the transfer.  For example, a transfer with 10 files of 300 MB each can be checked, but not a transfer containing a single file of 3 GB.

Please refer to the Pre-Processing Limit section to define how Cryptshare should process files that are larger than the processing limit of your virus scanner.

Panel
borderWidth1
titleAll System Settings

Children Display
alltrue
pageSystem Settings

Panel
titleTable of Contents

Table of Contents

Data Leakage Protection Integration

Data Leakage Protection (DLP) Tools can be integrated into Cryptshare using the pre-processing functionality. For example a tool which allows for data leak detection can be executed as a pre-processing command and be used to scan the transfer files that are being uploaded in order to remove files which are not allowed to be provided to others based on the exit code of the data leak detection tool.


Pre-Processing command

This is the command that will be used to check the file.
It is necessary to only type in the command as you would do in the Windows command line or Linux console.
Additional arguments for this command can be added by using the list-element right below the input field for the command.

Pre-Processing Limit

As some virus scanners are not capable to handle files beyond a specific size, a size limit for pre-processing files can be set. With this setting, size beyond this size will either be removed from the transfer or excluded from pre-processing.

Note
titlePerformance impact when scanning larger files.

Please note that increasing the limit for the file size to be scanned in the configuration of your virus scanner can have a considerable effect on the performance of the system, depending on your usage behavior. The size limitation of 25 MB has been set by the manufacturer of the anti-virus system, since viruses are usually spread over small files to spread them further, but seldom over very large files.

Different Exit Codes

By default, common applications use exit code '0' to indicate a negative match (i.e. no virus was found – the file can be encrypted).
Nevertheless some applications use a different exit code so the pre-processing result would indicate a virus where there is none. In this case you can change the exit code setting to correct false matches.

Notification

The administrator can be informed via email if pre-processing has excluded one or multiple files from the transfer.




Include Page
ATT:Footer
ATT:Footer
scrollEditorDisplayTitleThe content can't be resolved. The space ATT is not available in your include library.