Bad MD5 signature

When avast! Mac Edition tries to update the VPS data, a message appears “Bad MD5 signature The received VPS has wrong MD5 signature”. This is followed by a long string of numbers and letters starting “e”. The message then goes on to say “should be” and then is followed by another long string of numbers and letters starting with “4ecc”. The message then finally reports that the bad VPS was moved to my desktop as “400.vps.bad”. This problem started on 05/09 and happens every time avast! attempts to update the VPS data. What does it mean and why has it just started now? You can’t copy and paste the message from the window so I hope the above is enough info.

I received the same error. I ran the update twice and got the error both times:

The received VPS has wrong MD5 signature: e13860998256471a503bc9c1658d9b88 (should be 4ecc50008526047bf4738e843b9a8235).

The bad VPS was moved to

/Users/V/Desktop/400.vps.bad2

I update almost daily and have never had an error before.

For now, the problem (I assume) should be gone - right? If not, please, copy/paste the message with MD5 sums here, and also, check with cmdline utility the real md5 of the 400.vps.bad.

thanks,
pc

Yeah, so, I’m pretty much done with this. I’ve got the Windows edition installed on my PC and never ran into this. It seems that the Mac version is pretty lame.

Every day I get this message repeatedly: The received VPS has wrong MD5 signature: 06e4c24f53fb524de013b1fcc823ec78 (should be c4c9d31f98e0465d7fe90f7a647749bd).

Even when I manually hit the check update button, it takes a minute ‘checking for incremental update’ then gives me the exact same message. My virus definitions haven’t successfully updated since 7.08.08.

Lame. I think I’m going to ditch the Mac version and uninstall it.

That’s because windows version uses different update mechanism, which takes different files from different set of machines. In this version, the plain update style, as in Linux, was used - it simply downloads 400.vps from the server, and when there’s some corruption, it’s reported, that’s all.

In next version, the windows style will be used, because the amount of downloaded data is smaller (incremental update). This solution should be far less sensitive to such desync problems on our servers.

pc