You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to call the Windows Default Policy Module from within TameMyCerts, the former's registry settings need to be provided in the registry key of the latter.
In my own policy module I used registry symlinks like the one from CurrentControlSet to either ControlSet001 or ControlSet002 for that purpose. However ultimately that is an even worse solution than copying like Uwe does.
But I don't see the need to add that Properties GUI in TameMyCerts. All other settings of the Windows policy module have to be made via "certutil -setreg" (or some other form registry manupilation) anyways.
In this case
certutil -setreg policy\RequestDisposition +REQDISP_PENDINGFIRST
and
certutil -setreg policy\RequestDisposition -REQDISP_PENDINGFIRST
should do the trick.
We can try to just hand over the call to the Default Policy Module's one. For the meantime, certutil does the trick as @hansjoachimknobloch pointed out.
When running the install.ps1, it copies the registry, including:
And to change it back, one needs to either uninstall and change, or hack the registry
The text was updated successfully, but these errors were encountered: