Author Topic: 400.vps.bad  (Read 12448 times)

0 Members and 1 Guest are viewing this topic.

Offline .: Mac :.

  • Avast Überevangelist
  • Ultra Poster
  • *****
  • Posts: 5087
400.vps.bad
« on: May 11, 2008, 04:30:58 AM »
Im getting these files created on my desktop. 400.vps.bad, 400.vps.bad1, etc. Im assuming its happening when the automatic VPS update fails as usually when they appear I can see that the VPS is a day or so old.

Running the Manual update usually will clear everything up for a few days then they appear again.

This is on Mac OS X 10.5.2 (Intel)
"People who are really serious about software should make their own hardware." - Alan Kay

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: 400.vps.bad
« Reply #1 on: May 13, 2008, 12:32:03 PM »
Hallo, that 400.vps.bad file is a freshly downloaded new VPS which was checked and found corrupted.

This means that the VPS was downloaded but is probably unusable (using it would be security sirk, because its contents might be forged/malformed). Thus, it's labelled "bad", placed on desktop (for further analysdis what happened and/or what was actually downloaded) and the original vps (which was included in the installation package and was proven correct) is used instead as a fail-safe replacement. Try to push "check update" button and download it again.

Btw. please, send the 400.vps.bad file to me (cimbal@avast.com) for further analysis, what went wrong.
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)

Offline .: Mac :.

  • Avast Überevangelist
  • Ultra Poster
  • *****
  • Posts: 5087
Re: 400.vps.bad
« Reply #2 on: May 13, 2008, 04:04:35 PM »
Sent by email, Thanks
"People who are really serious about software should make their own hardware." - Alan Kay

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: 400.vps.bad
« Reply #3 on: May 14, 2008, 09:35:34 AM »
Sent by email, Thanks

Hmm, I have got nothing so far - maybe the address was wrong, or the size of attachment was over some limit on your SMTP gateway?

Anyway, the 400.vps.bad, when created, is also allerted with a window that says what MD5 was expected, and what MD5 was conmputed from the particular file. Then, check it from terminal using md5 utility, whether the file is really bad - and in this case, send it (preferably zipped) to cimbal@avast.com, thanks in advance.

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

Offline .: Mac :.

  • Avast Überevangelist
  • Ultra Poster
  • *****
  • Posts: 5087
Re: 400.vps.bad
« Reply #4 on: May 15, 2008, 04:34:54 AM »
Sent by email, Thanks

Hmm, I have got nothing so far - maybe the address was wrong, or the size of attachment was over some limit on your SMTP gateway?

Anyway, the 400.vps.bad, when created, is also allerted with a window that says what MD5 was expected, and what MD5 was conmputed from the particular file. Then, check it from terminal using md5 utility, whether the file is really bad - and in this case, send it (preferably zipped) to cimbal@avast.com, thanks in advance.

pc

hmm Apple's .Mac SMTP servers attachment limit is 20MB so it should have been fine, ill zip and resend might have been the double file extension getting blocked.

Ive not seen the box with the MD5 error, most likely because this is happening on the auto update when im away from the computer. but here is the terminal output showing the MD5 of the 400.vps.bad file:
Code: [Select]
Last login: Wed May 14 22:28:17 on ttys000
kyle-barkers-mac-mini:~ Kyle$ cd desktop
kyle-barkers-mac-mini:desktop Kyle$ MD5 400.vps.bad
MD5 (400.vps.bad) = e13860998256471a503bc9c1658d9b88

"People who are really serious about software should make their own hardware." - Alan Kay

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: 400.vps.bad
« Reply #5 on: May 15, 2008, 11:02:34 AM »
Sent by email, Thanks

Hmm, I have got nothing so far - maybe the address was wrong, or the size of attachment was over some limit on your SMTP gateway?

Anyway, the 400.vps.bad, when created, is also allerted with a window that says what MD5 was expected, and what MD5 was conmputed from the particular file. Then, check it from terminal using md5 utility, whether the file is really bad - and in this case, send it (preferably zipped) to cimbal@avast.com, thanks in advance.

pc

hmm Apple's .Mac SMTP servers attachment limit is 20MB so it should have been fine, ill zip and resend might have been the double file extension getting blocked.

Ive not seen the box with the MD5 error, most likely because this is happening on the auto update when im away from the computer. but here is the terminal output showing the MD5 of the 400.vps.bad file:
Code: [Select]
Last login: Wed May 14 22:28:17 on ttys000
kyle-barkers-mac-mini:~ Kyle$ cd desktop
kyle-barkers-mac-mini:desktop Kyle$ MD5 400.vps.bad
MD5 (400.vps.bad) = e13860998256471a503bc9c1658d9b88



Have got it from .:Mac:., thanks.
The downloaded 400.vps was truncated at cca 30% of its nominal size, and that was why it was reported as corrupted. Now it's time to check for the cause of such corrupted downloading...

zilog@zilog:~$ ls -l 400.vps.bad
-rw-r--r--  1 zilog users 5160960 May 10 03:38 400.vps.bad
zilog@zilog:~$ printf %x 5160960
4ec000

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

Offline roj37

  • Newbie
  • *
  • Posts: 1
Re: 400.vps.bad
« Reply #6 on: July 16, 2010, 10:09:23 PM »
thank for detail . :)