Jump to content

igelskalar

Members
  • Content Count

    3
  • Joined

  • Last visited

Profile Information

  • Location
    Germany
  1. Now I was able to find a solution by myself: The installation created at symlink named /opt/eset/efs/sbin/cls/lib pointing into the void, but the right lib directory containing the virus definitions was found in /var/opt/eset/efs/lib. So I recreated the symlink in /opt/eset/efs/sbin/cls/lib with ln -sf /var/opt/eset/efs/lib /opt/eset/efs/sbin/cls/lib and so got the cls CLI-Scanner working. Best regards, Sascha
  2. Thanks for your reply, but I get the following error message when executing /opt/eset/efs/sbin/cls/cls: ECLS Command-line scanner, version 1.0.0.0, (C) 2017 ESET, spol. s r. o. Scanner initialization failed. And as I stated above, strace reveals that the scanner was looking for a file called em000_64.dat, but fails. Best regards, Sascha
  3. Hello there, is there any working command line scanner which can be integrated in a running postfix/amavis configuration? I evaluated Mail Security für Linux but it obviously gets not longer updated anymore. Now I tried to give a chance to File Security für Linux, it comes with this odscan CLI-tool, but it is not reporting neither success nor any resulting virus status. There is also a integrated tool called "cls" in the /sbin folder of the installation directory, but this one obviously does not find its virus databases as it is looking for "em000_64.dat". Best regards Sascha
×
×
  • Create New...