Im trying to automatize in a legitimate way, the interaction of my program with avast and the user. The process to add it in the exclusion list manually is a bit difficult for some user (even with a video-tutorial).
I’m making a parser for the FileSystemShield.ini where the path will be added to the ScanExceptions rule. But i come up with a question…
I think the file FileSystemShield.ini does not always exits if the settings dialog has never been opened, and because the Avast Self-defense module, i cannot create it neither…
Is there any cleaner solution rather than disable the avast-selfmodule in the avast5.ini file and that doesn’t implies (or at min as possible) the interaction with the user??
AFAIK only notepad can edit those *.ini files of Avast if the self-defense module of Avast is active/enabled (which is the recommended and the default too).
I guess (or hope ? ) this is not going to be a simple task to achieve. If “anything” could change Avast settings, then many vulnerabilities would be opened.
I dont really think that allowing to write only to notepad would protect your computer at any point… there are many ways to pass that over… As I said before I want to do it cleanly…
In addition, one should think if protecting a computer means to put constraints on the way with the user… If there is a popup confirming to the user every action why dont provide an API to interact with?