Author Topic: All this mess because I rename a .dmg?  (Read 2308 times)

0 Members and 1 Guest are viewing this topic.

Offline candylovergirl

  • Newbie
  • *
  • Posts: 13
All this mess because I rename a .dmg?
« on: June 02, 2019, 11:03:09 AM »
Hello,

When I run a Full System Scan, Avast is unable to scan some files, with terrific errors like "bomb", "corrupted" only because I renamed  SecUpd2019-003HighSierra.dmg for something else ending of course in .dmg??  :o >:(

What these fatalistic errors really means or why Avast is unable to scan, this is only a clean macOS HS 17G7024 install!!  >:( :o

Update: I found the solution here
https://forum.avast.com/index.php?topic=227372.msg1506736#msg1506736




 
« Last Edit: December 06, 2019, 12:53:07 AM by candylovergirl »

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 75541
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
W8.1 [x64] - Avast PremSec 22.5.7263.B [UI.706] - Firefox ESR 91.9.1 [NS/uBO/PB] - Thunderbird 91.9.1
Avast-Tools: Secure Browser 101.0 - Cleanup 22.2 - SecureLine 5.18 - Driver Updater 22.2 - CCleaner 6.0
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline candylovergirl

  • Newbie
  • *
  • Posts: 13
Re: All this mess because I rename a .dmg?
« Reply #2 on: June 02, 2019, 11:21:43 AM »
-> https://forum.avast.com/index.php?topic=227372.msg1506736#msg1506736

Ok that is very nice

The "archive is corrupted" error simply means that the scan could not unpack the archive file, not that the file is corrupted. This most often happens when a proprietary file compression system is being used.

The "The file is a decompression bomb" error does not usually mean that the file actually is a decompression bomb (https://en.wikipedia.org/wiki/Zip_bomb). Typically, this error occurs with heavily compressed files as they can bear some resemblance to a decompression bomb. As a compression bomb works by overloading the system when it is unpacked, the Avast scan does not unpack these files simply as a precaution.

If there was something malicious embedded inside the compressed files, it will be identified if/when the file is unpacked by another program (as the File Shield will scan any compressed file at the time that it is unpacked). Therefore, it is safe to ignore these "unable to scan" results.

Isn't should be better to see in the results Avast could not unpack this archive file?

or

Avast scan does not unpack these files simply as a precaution?? and not BOMB?

It really scares the users!!

If there was something malicious embedded inside the compressed files, it will be identified if/when the file is unpacked by another program

What if I ins†all the update before avast antivirus????

Very disappointment, because I really love avast in my Windows PC, but in macOS eww  :P

Came


« Last Edit: June 02, 2019, 11:26:25 AM by candylovergirl »

Offline .: Mac :.

  • Avast Überevangelist
  • Ultra Poster
  • *****
  • Posts: 5093
Re: All this mess because I rename a .dmg?
« Reply #3 on: June 23, 2019, 02:35:53 AM »
I believe its been mentioned that a future release will be less verbose on these messages. This has been a constant question since the first Avast for Mac back in the 4.x engine days
"People who are really serious about software should make their own hardware." - Alan Kay