@
SugarD-x, in Reply#1
I'm one version behind, see my sig, not many. Will update soon. I doubt this is the cause of all this strangeness.
@
Charyb, (post above this one)
I know. Many config files are associated with not what they're supposed to be

I didn't design windows. No, really, it usually works just fine for firewall config (MS Outlook association), some other config files in in XML format (windows sees is as associated with XML editor, which it's not), and various others.
So most unlikely avast would have an issue with .BIN file here. If avast does, then indeed we have a problem.
@
DavidR and RejZoR,
- Normal Avast updates normally come come in. Avastsvc.exe launches avast.setup, communication is over TCP, outbound to one of several avast servers. Directly to avast IPs, no proxy. All allowed, not logged.
- Emergency updates are by TCP through the avast proxy port. Don't ask why. I have no clue. I don't care. Having read, long ago, what it's about, when my Firewall alerted, I made a rule to permit and log since emergency updates are infrequent, except what's in this thread.
- Inbound connections are not needed, unless I run a server of some sort. If they were for Avast, I'd ditch avast. Once you establish outbound to avast server (direct or through the proxy port), replies (updates) come in. True for outlook mail, gmail, web pages, really any internet stuff. Avast NEVER asked for any incoming connection to my box. It doesn't want it. It doesn't need it.
- Bit more review of what I have:
When my firewall watches behavior it reports it in the text file in addition to the behavior log. The log rolls over, so all I have is since Oct27. It's easier to extract the events from the text file, so here it goes:
This is how it used to be, 14 emergency jobs in 10 days more or less - see attached
FW-systemlog1Then the flood began with something downloaded to the \temp directory, sure looks weird, I hope it's not some trojan I'm happily allowing.
The .exe files aren't there any more, so I can't even upload to virustotal.
Since it came in, I have that flood I reported. Perhaps Avast changed the meaning of emergency updates and uses the application for streaming as well?
Several, not all, are followed by the normal update event like this
[13/Nov/2012 13:15:28] DriverEventHandlersImpl.cpp: "System" action = 'permitted', operation = 'creating_proc', proc = 'c:\Program Files\AVAST Software\Avast\AvastSvc.exe', subj = 'c:\Program Files\AVAST Software\Avast\Setup\avast.setup'
see attached
FW-systemlog2