Defense+ keeps asking in MinGW build process
OK, I am a developer and using the GCC/MinGW tool suite under Win32 (from http://www.mingw.org). Whenever I build application that use the MinGW “make” application which itself may call applications like “makedir.exe” to create output folders find myself in an endless loop of CIS/Defense+ asking me a million times for temprary batch files created by MinGW/make.
I’ll try to explain what happens:
1.) I call a Makefile that will call other applications e.g. for creating directories, grabbing version information or alike.
2.) MinGW/make will create temporary Makefiles during the build (usually something like make-1234-1.bat) in the TEMP folder with a random number.
3.) These batch files will call sub-steps of the compilation, e.g. another makefile, the compiler or alike. It even will create “protected” files" like DLL’s or applications in the build process.
4.) As the parent application (the batch Makefile) always changes, CIS/Defense+ keeps asking me what to do (see images MinGW_build_1.png and MinGW_build_2.png attached). This never ends and massively slows down the build process in addition.
5.) I have a bunch of rules created (DefensePlusRules.png) all not applicable next time, as the names of the batch files are random.
For the moment I always have to disable Defense+ whenever I build applications using make. This is rather annoying, so my question is: (How) can I create a (one) rule that manages this CORRECTLY?
- Screenshots illustrating the bug: Appended
- Screenshots of related CIS event logs or the Defense+ Active Processes List: Not applicable
- A CIS config. report or file: Not applicable
- Crash or freeze dump file: Not applicable
- Screenshot of More~About page: Appended
- CIS version, AV database version (See screeenshot) configuration used: Internet security
- Ave you made any other major changes to the default config (eg ticked ‘block all unknown requests’, other egs here.): No
- Defense+, Sandbox, Firewall & AV security level: D+=Safe, Sandbox=Disabled, Firewall=Custom policy, AV=Stateful
- OS version, service pack, number of bits, UAC setting, & account type: Windows XP, SP3, 32 bit, None in XP, Default user (non-admin) account.
- Other security and utility software installed: Nothing
- Virtual machine used: Not applicable
[Edit: More precisely explain the screenshots.]
[attachment deleted by admin]