Thanks RejZoR for your comment. Seems rather in line with what you've been saying from the begining and on several places in this very thread. If I understand you correctly, you'd suggest to not limit CC to downloaded files only and expand the backends accordingly. Do you have any suggestions how to handle the case where the file it self requires dependencies to be run (such as .DLLs in the same folder) ? Would that be ok for you if CC will submit the whole folder - or would you consider that as a privacy issue?
Thanks.
Lukas.
BTW: Be Secure - I got the logs from you, thank you!
Yeah, I think that way because of all the problems I've seen so far and because of the CyberCapture dependencies...
You have to have CyberCapture enabled, Web Shield installed (a lot of people leave just File System Shield) and the file has to arrive from a download. Just too many things that can go wrong along the way or be missing. Connecting CyberCapture to the File System Shield would make more sense.
As for DLL's, can avast determine DLL dependencies for EXE to run or would it just blindly upload all of them from that folder? If you limit the file collection to DLL's only, I think it should still be fine, but I don't think people would want their other data files to be uploaded. Besides, DLL's can often operate as injectors for legit apps which can be used by malware. So, that would be one of reasons why uploading them would make sense.
What I'm more worried with such extended scope of upload, people with limited bandwidth. I personally don't care as I have unmetered line, but not everyone has it like I do. Not sure how to make that functional without eating their whole monthly bandwidth...