|Main Archive Page > Month Archives > clamav-users archives|
On 4/16/10 23:18 , Chuck Swiger wrote:
> On Apr 16, 2010, at 1:42 PM, Giampaolo Tomassoni wrote:
>>> The owner of the box. They may not be qualified to manage the machine,
>>> but computers don't plug themselves into the network-- every machine
>>> belongs to someone who pays for electrical power and network
>> What if your PS3 stops working because the maker thinks it is a too-old
>> model to still go?
> A fine question. Let's suppose a certain old PS3 model has a serious manufacturing defect, such that it can overheat and catch fire.
> Let's suppose Sony starts releasing firmware updates on new games, or via network updates, etc, which check for the presence of the defect and produce a big red warning on the screen saying, "This machine has a problem and it needs a human to check and fix it." They don't stop you from playing your game, but they have been trying hard to catch your attention.
> Six months later, Sony releases a new game which happens to really beat on the PS3 and is pretty likely (or even dead-certain) to cause machines which have this problem to catch fire. Should Sony release firmware which causes the PS3 to refuse to run this game?
>>>> If nobody had to turn off freshclam, why clamscan had to stop working?
>>> Sufficiently old versions of ClamAV don't work with all of the current
>>> signatures, and bugs in these old versions prevent the ClamAV team from
>>> writing more complex signatures that they would like to use.
>> Just prevent old versions from upgrading. It is not that difficult.
> I agree with you entirely. You're welcome to roll back to the 2010-4-14 virus signatures before the less-than-0.95 kill switch was turned on, and your outdated ClamAV will continue to run just fine with these old signatures.
Just one remark: Anyone Ran Linux on their PlayStation lately?