The ebuild still searches in ftp://ftp.bitdefender.com/pub/linux/free/bitdefender-console/en/ but the files have moved to ftp://ftp.bitdefender.com/pub/unices/old/linux/free/bitdefender-console/en/ (i think because of the release of bitdefender 10)
The old version isn't able to recognize newer viruses. The new one is the way to go, although is not free anymore (you must purchase a license after a evaluation period of 30 days).
I'm planning to give up maintainership of this and announce its masking on -dev soon. I can't support a payware product which I am not planning to pay for, can I?
The funny thing is bdscan --info keeps spitting out the output below, no matter how many days have past since installation ;) tsr ~ # bdscan --info BitDefender Antivirus Scanner v7.60825 Linux-i686 Copyright (C) 1996-2006 Softwin SRL. All rights reserved. Trial key found. 29 days remaining. ... I think it is worth having it into the tree. The new SRC_URI is http://download.bitdefender.com/unices/bdscan/final/en/Linux/BitDefender-scanner-7.5-4.linux-gcc3x.i586.tar.run .
Ok, I started working on the ebuild - they have changed quite a lot since 7.0 or 7.1. I am thinking of just creating a new package, app-antivirus/bitdefender-scanner.
I dropped bitdefender and I'm in the process of migrating to clamav. You are supposed to buy a commercial license from them if you wanna use it in commercial purposes. I contacted them and they told me this product is not entirely supported, but I asked for a proforma anyway. They told me I will receive it on my mail, but after more than 3 business days nothing has happened. There was a time when bitdefender was selling some pretty neat stuff and when their CD was a Linux Defender bootable disk. Now their Linux Defender is obsolete (I didn't found SATA support that I needed on that customized *old* version of Knoppix) and they don't seem to care about it. I've had it. I'm no longer care what you do with this package.
I have unmasked bitdefender-console-7.1, which is still a free product. The collision issue was worked around by conditionally installing malware definitions - see the ebuild, and bug #158219, comment #5 for details. Thanks for the patience, everyone.
