Hi,
our office is currently running Comodo 5. I have written a Python script to automate the compilation of our software and generation of a NSIS installer ( NSIS Wiki ). When the script tries to compile the installer, Comodo keeps popping up the message below. If I “OK” past this message, this allows the installer to be successfully created. However, it is not much of an automated system whenever someone has to be at the computer to watch while it compiles and then manually tell Comodo to permit the installer to be created. Can anyone help please? I have also attached the Defense+ event logs.
Thanks,
Patrick
Hi Dennis2,
I did as you suggested: I went to “c:\windows\system32\cmd.exe”, and altered the “Run an executable” command to add “C:\Users<current_user>\AppData\Local\Temp*.tmp”. The problem, however, still persists. Perhaps this says that all existing *.tmp files at that location are ok to run, but every new .tmp file being generated there by the Nullsoft installer still comes through as being unrecognised and needing to be allowed to run by Comodo. Do you have any other suggestions?
Thanks,
Patrick
I have noticed something here that hopefully may be helpful. If I add the *.tmp line as shown below, then ok and apply all the way out of the dialogs, if I now immediately navigate directly back to that same location, the *.tmp line will have been replaced with a list of all the existing individual .tmp files in the Temp directory. This to me suggests that all existing .tmp files are fine for Comodo usage but new ones are still unrecognised.
I just tried to change the line to “C:\Users\Patrick Steele\AppData\Local\Temp*”, closed all the Comodo dialogs, navigated back to the “Run an executable” dialog and yet again the line that I had added was now replaced with a list of existing .tmp files. Surely that is a bug?
edit file path dialog
C:\Users\Patrick Steele\AppData\Local\Temp*.tmp
ok
run an executable dialog
ok
customise policy dialog
ok
application system activity control dialog
apply
computer security policy dialog
close
comodo firewall dialog
close
When I go back to run an executable dialog, it has again removed the line I edited and replaced it with a list of existing .tmp files.
The only thing I could think of myself as the settings are not being saved it could be a permission problem as the configuration is saved in the registry.
Aha! I found it! I checked where the comodo registry settings were and noted that on exiting out of the Comodo dialogs as per the list above, then the registry was unaffected. I tried again and then noticed that the “Computer security policy” dialog has an “OK” button down at the bottom. I had not spotted that before and instead had been closing the dialog up top, which must have been the equivalent of sending out a cancel event. Sorry to trouble you Dennis and thanks for all the help! Now I really can have an automated software generation system
Patrick
