Good news, everyone!
avast! is proud to introduce you the new linux server product line for 2014:
avast
The avast package provides the core scanner component and a command line scan utility. It can be used for on demand scanning or mail server integration using amavis.
New since previous version:
Avast 8 engine
Native x86_64 support
Differential VPS updates
avast-proxy
The avast-proxy package provides a transparent network traffic filtering proxy designed for gateway/router usage. Using avast-proxy, you can scan a whole computer network traffic from a single machine including secured connections!
Core features:
HTTP, IMAP and POP3 protocol support
Support for secured connections (uses certificate resigning)
High performance - designed for typical LAN usage
Well tested - daily used by almost a milion avast! for Mac users
avast-fss
The avast-fss package provides a fanotify based „on write“ filesystem shield designed for fileserver usage.
The typical target field for avast-fss are SMB/NFS file servers.
x86_64 and amd64 are the same architectures. The difference is only the package naming convention on Debian/RHEL.
In other words, both packages will work on AMD and Intel CPUs.
Note: In the final release, there will be also packages for the i386 architecture.
I just wanted to shine some light for you guys on AMD64. AMD64 is software extensions that allow 64 bit code to run on 32 bit processors. So, in x86 architecture, there are no 64 bit AMD CPUs, and there are no 64 bit Intel CPUs. Intel EMT64 is the AMD64 code relicensed to Intel, so they may also run 64 bit code on their 32 bit processor. They are exactly the same. The only 64 bit CPU is the Intel Itanic, but it is not x86 architecture.Sincerely,
J.R. “AutoSandbox Guy” Guthrie
“At this point in time, the Internet should be regarded as an Enemy Weapons System!”
The license must be located at /etc/avast/license.avastlic, its printed
into the console when you install the deb/rpm package. Additionally you can
find this info in the README file at /usr/share/doc/avast/.
The reason why retrieving the VPS version (scan -V) does not work is most
probably that the avast scan service is not running because it can not find the license
file. See the system log file (avast uses syslog) for details.
I have no idea how that project works, but If all you need are MD5 hashes of infected files, than you can scan a file using avast and compute the file’s hash using md5sum, if the file is reported as infected.
I think you may need to rename license.avastlic.txt to just license.avastlic before copying across to /etc/avast as tumic advised above. That is the name the avast.conf file seems to be looking for.
Also reboot. That got avast running for me, and scanning now seems to work.
avast! version 4 VPS will be available until there are any avast! products using it, including windows products.
At the moment there are still such products, but the maintenance is very limited. So the new linux products are
not the final nail in the VPS 4 coffin, but a very significant one.