I think that the addition of Edit ability for remember rules at D+ Popups would be a good improvement, especially for the advanced users that use Safe/Paranoid modes…
An application (wanted) executed tries to modify 15 REGISTRY VALUES AT THE SAME PROTECTED KEY… You have to answer to 15 pop-ups. The other way to go is to answer the first pop-up with remember rule & then go to defence+ settings, find the application, and after too many clicks edit the access rule for the protected registry with some wildcard * or something…(too difficult, because of the many pop-ups appear at the same time)
An application (wanted) executed tries to modify 15 REGISTRY VALUES AT THE SAME PROTECTED KEY… At the first pop-up you press a (new) EDIT-click and you edit the rule as you like, with wildcards, files/folders/registry directories, whatever. No second pop-up appear…
(edited, tried to repair my fault about registry VALUES-KEYS)
There is an easier way. In one of the popups, (when you realize it’s going to ask for permission a bunch of times) change the policy to ‘trusted application’. It will stop asking for permission to access all those registry keys.
Yes, i know this. But if i trusted every application, I shouldn’t use D+ at paranoid mode :■■■■
Simple scenario1: an application needs full access to a registry key (lets say 20 values) and the user would like to allow access only for that particular key, not elsewhere.
Simple scenario2: an application creates various files in a particular directory with D+ warnings for each file and the user would like to allow access only for that particular directory… etc
The most important for me should be the ability to edit the path (for registry or directory) at the pop-up and add a wildcard *
Oh, I see now…
I thought you were wanting to wildcard all registry key access, which wouldn’t be any different than the trusted application policy.
Wildcarding a particular key or directory makes sense.
+1, Sounds reasonable.
Thanx HeffeD & Joker, it was my fault at the first post (registry values & keys), sorry, tried to repair it (not native english speaker also ???)
I think that it is clear now :■■■■