V2.0.4: fix non utf8 clamscan output in archive filenames (-a)

2.0.4 version :

-  test build with clamav 1.1.0 engine
-  fix amazonlinux2 default yum timeout cause build to failed in docker when servers was too busy
-  fix urllib3 to 1.26.16 because 2.0.0 need ssl requirements not meet in aws 3.8 python at runtime
-  fix clamscan output cause lambda to failed at runtime with following error when binary file is considered as archive and file_names displayed contains
   non utf-8 decodabled bytes sequences:

Starting clamscan of /tmp/xxxxx-antivirus-scan-prd/xxxxxxxxxxxxxxxxx/contents/xxxx/fichier2.mp3
[ERROR] UnicodeDecodeError: 'utf-8' codec can't decode byte 0x83 in position 249: invalid start byte
Traceback (most recent call last):
File "/var/task/scan.py", line 247, in lambda_handler
scan_result, scan_signature = clamav.scan_file(file_path)
File "/var/task/clamav.py", line 192, in scan_file
output = av_proc.communicate()[0].decode()

cloud4t0r 2.0.3

add rust dependancy for 0.105+ compilation in dockerfile

cloud4t0r 2.0.2

• the compilation processus now take care of clamav >= 0.104 CMAKE syntax

cloud4t0r 2.0.1

cloud4t0r version

2.0.1 version :

• the lambda.zip file is now obtained by recompiling the sources of the last commit of the most recent stable branch and not at all while unpacking an old version of rpm EPEL from RHEL7

• The code has been revised to be able to use version 3.8 of the AWS lambda runtime and last version of requirments

• all the executables and embedded libraries have been stripped

• python cache files (.pyc) have been excluded from the generated zip

you should no longer have a warning in the lambda log that the scan engine is out of date, just after installing it

all the original documentation that follows is still valid except that you must now use the Python 3.8 instead of 3.7 Runtime while creating the lambdas functions.