Author Topic: "Bad MD5 Signature"?  (Read 7245 times)

0 Members and 1 Guest are viewing this topic.

Offline MikeMoyle

  • Newbie
  • *
  • Posts: 1
"Bad MD5 Signature"?
« on: September 21, 2008, 01:26:18 AM »
For the past several days, I've been receiving the following error message when trying to update Avast:

"The received VPS has wrong MD5 signature: ---------LongHashNumber---------
 (should be ---------DifferentLongHashNumber---------)."

Any ideas on what might be causing this, and suggestions on fixing it?

FWIW, I'm running a registered version of Avast Version 2.74R0 (ServiceKit 1.41) on OS X 10.4.11, with all patches up to date.

Offline ardvark

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1512
  • John 3:16 (I'm not an "avast! evangelist")
Re: "Bad MD5 Signature"?
« Reply #1 on: September 21, 2008, 08:05:52 AM »
Hi...

I would first try to perform a repair installation, if avast under OS X offers this operation. If not or this does not fix the problem, you can try uninstalling avast and then reinstalling from scratch.

I have no idea as to what has caused this problem, though. ???

Best Regards...

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: "Bad MD5 Signature"?
« Reply #2 on: September 22, 2008, 05:53:10 PM »
For the past several days, I've been receiving the following error message when trying to update Avast:

"The received VPS has wrong MD5 signature: ---------LongHashNumber---------
 (should be ---------DifferentLongHashNumber---------)."

Any ideas on what might be causing this, and suggestions on fixing it?

FWIW, I'm running a registered version of Avast Version 2.74R0 (ServiceKit 1.41) on OS X 10.4.11, with all patches up to date.

Hallo,
it's in most cases some problem in the network (which causes data corruption, case A), or some temporary desync on our servers (caused by a malfunction of particular machine(s), case B). Just check the bad vps (was copied to your desktop) - does it end with ASWSignd?

If so, it's probably complete file, and thus case B, otherwise it's probably case A. Both problems are transient, and B should disappear as soon as we 'll fix the desync.

In case B, you can just quit the app and agent,. and copy the "allegedly bad vps" from desktop to ~Library/Application Support/com.avast.MacAvast - and it would be probably accepted by the app with no problem...

regards,
PC
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)