Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properties from Windows default policy module missing #36

Open
virot opened this issue Oct 29, 2024 · 2 comments
Open

Properties from Windows default policy module missing #36

virot opened this issue Oct 29, 2024 · 2 comments

Comments

@virot
Copy link
Contributor

virot commented Oct 29, 2024

When running the install.ps1, it copies the registry, including:
image

And to change it back, one needs to either uninstall and change, or hack the registry

@hansjoachimknobloch
Copy link

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.

@Sleepw4lker
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants