I just mean that my file defense rules allow avast.setup to modify any files of avast!
Ok, but it's a .setup file and not .bat, .com, .vbs, .exe and so on that could manage avast executables. Of course, avast programmers could drop a word here. I'm trying to 'defend' the use of avast.setup as being safe. But I could be wrong and, in this case, it would be good that Alwil team say something about security issues and holes while using a temporary file during update.
