bitdefender-console-7.01, when installed, does not reflect that it requires signature updates. In testing, BDC seems to have a dependency on the date/time stamps of all of the "plugins" that provide anti-virus protection. The ebuild does not appear to preserve the date/time stamps for each Plugin/* file from the tar file: when installing the ebuild, all files are given the system date/time of installation. In testing, BDC seems to use filesystem date/time stamps to determine whether signature changes are needed. Unless timestamps are set correctly on these files, it may obscure signature updates for a significant amount of time, creating a security vulnerability in BDC users. Reproducible: Always Steps to Reproduce: 1. emerge bitdefender-console 2. /opt/bdc/bdc --update 3. touch -t 200401010000 /opt/bdc/plugins/* 4. /opt/bdc/bdc --update Actual Results: BDC reports no updates available until date/time stamps are reset, or until a new update is available. (PROBLEM: this may be a long time). Expected Results: BDC should realize it needs to update to more current signatures. Seems to me that this can be fixed in several ways. One way is to convince 'tar' to preserve the date/time stamp when extracting BDC. An easier, short-term hack would be to touch all files in /opt/bdc/Plugins, so that the timestamp is set to a point sufficiently in the past that updates will definately be newer.
Hm, works for me - after a clean bitdefender-console install, bdc --update updates quite a bunch of files.
After repeated attempts on several boxes to reproduce this, I wasn't able to. Sorry.
