I checked and searched for following:
Giving an application rights just like trusted application, but STILL being asked upon start of a replaced program.
I search for a setting that allows open-create and open-modify of .exe .com etc, but does NOT update the stored hash of the modified programs.
It is like limited trust, what happens if the “trusted” program runs havoc (i.e. due to a plugin in the trusted program which behaves like a virus), modifies tons of programs, and I don’t notice.
This between way of policy is missing.
A lot of programs need “trusted” rights, like Filemanagers, Adobe Updaters, which cannot copy a .exe file when they are not trusted. But it shouldn’t updating the hash of the copied programs not yet, ask extra after replacement and upon start of the replaced program.
Or other way to say: Either I set “trusted program” or “Installer” and it can modify anything it wants in the whole system (and not only what I want) without control due to auto-update-hashes, or the program is not trusted and I cannot even use a filemanager.
The “trusted program” and “Install mode” the way they are now is perfect for Windows updates, or Windows Service Packs, Virus scanner and other system-near stuf. For all other things the “Limited trust” with still asking after replacing a .exe file is what paranoid-mode should be, maybe even what “safe mode” should be. I want to control what they replace, and I cannot right now, for me I would impose “limited trust” even to explorer.exe or my winrar.exe example to ask me “File replaced, accept new version?” AFTER I copied it.
So, now that I said four times basically the same things just in different word in one post, please help!
How can I set such a policy, currently it seems impossible “by design”.
Set
PS: Yes, yes, I am a control freak and paranoid, the better you know computers, the more you get that way.
PS2: Your wiki on http://wiki.comodo.com/CFP3/Help_Guide/Defense_Task_Center/Defense_Settings#.27General_Settings.27_tab says that DNS recursion can be used as an attack vector. It can also be used as VPN, altough this is kind of sick. There are test implementations which are very good functional to create a full tunnel (not nessecarily encrypted) by only using DNS requests, without having any gateway configured at the machines using that sick tunnel way. Since DNS is required for Active Directory usually the AD-Server doing the DNS-Server also does forwarding DNS to an external Server for unknown domains (else nobody could surf or get Windows updates), so this attack vector is normally open.
See http://www.heise.de/ct/inhverz/suche?q=dns+tunnel&search_submit=Suchen&rm=search (sorry, German Magazine, and the online version of that article costs money, I still have that issue on paper here).