mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #104] Windows10 Professional 64-bit can not install CA certificate #57
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wickpwn on GitHub (Jan 8, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/104
C:\WINDOWS\system32>mkcert -install
Using the local CA at "C:\Users\pwn\AppData\Local\mkcert" ✨
ERROR: add cert: Failed adding cert: The access control list (ACL) structure is invalid.
I tried to search for google-related unsolvable (ACL) issues, but did not find a suitable solution.
@modernist commented on GitHub (Jan 8, 2019):
+1. Running the tool with administrator privileges and setting the security permissions on the AppData\Local\mkcert folder does not help either.
@mdkozlowski commented on GitHub (Jan 8, 2019):
Same problem, both with binary built from source in Go 1.11.4 and on the pre-built binaries.
@adamdecaf commented on GitHub (Jan 8, 2019):
cc @cretz Do you have any ideas?
@cretz commented on GitHub (Jan 8, 2019):
Hrmm, I haven't used the tool in a bit. I will investigate at some point this week. I wonder if a recent update caused this as I had used it with success many times on win 10 before.
@cretz commented on GitHub (Jan 8, 2019):
I am having trouble replicating on win10 pro. It works fine for me. Y'all's error message appears to be from CertAddEncodedCertificateToStore and my research says it is due to some registry ACLs. I see a post with suggestions on resetting some ACLs to fix it, but I can definitely understand a fear of blindly trusting it.
If I must I can give a tiny bit of Go code or C++ code or whatever that y'all can pass to MS since this seems to be a Windows error.
@cretz commented on GitHub (Jan 8, 2019):
If someone wants to try it since I cannot replicate, download SubInAcl, then run:
Click to see my output to compare
That's just a guess, there are other registry keys that may be touched too. Based on that previous answer, if anyone having this problem is willing, please run the following and see if it fixes it:
and
@wickpwn commented on GitHub (Jan 9, 2019):
Hello, I found this answer yesterday, but still can not solve, I checked the folder permissions no problem, the problem has been submitted to Microsoft, I hope they can give a solution!
@wickpwn commented on GitHub (Jan 11, 2019):
Solution: Switch to the highest privilege account Administrator to install successfully, you can not switch to other accounts under the highest account installation, so the certificate will still be invalid, please ensure that the system under the highest privilege account operates.
Iis related tutorial:https://medium.com/@aweber01/locally-trusted-development-certificates-with-mkcert-and-iis-e09410d92031
@cretz The mentioned SubInAcl only supports the following systems: Windows 2000, Windows Server 2003, Windows XP
@swiftdv8 commented on GitHub (Jan 11, 2019):
@wickpwn solution is not working for me: Im logged in as my admin account and running
mcert -installin an Admin Command prompt and still gettingive tried with a couple of different mkcert releases with the same result
Please let me know if there is something I missed
@wickpwn commented on GitHub (Jan 11, 2019):
按照这个操作解决(https://answers.microsoft.com/zh-hans/windows/forum/all/%E5%AE%89%E8%A3%85ca%E8%AF%81%E4%B9%A6%E5%A4%B1/e23cc521-b3f7-4ac6-8519-b75a11b944ac)
@natiki commented on GitHub (Mar 14, 2019):
FWIW https://github.com/FiloSottile/mkcert/issues/148 I used the Scoop install and then a regular user account and Powershell and had no issue. My user account is part of the administrator user group. No other changes needed.
@axi0m commented on GitHub (Jun 14, 2019):
I ran into the same error.
OS Version
My workaround was to simply take the
rootCA.pemfile and import using the same Administrator PowerShell prompt I had open to install mkcert via choco, via PowerShell cmdlet@rfay commented on GitHub (Nov 10, 2019):
We
mkcert -installon both Win10 Pro and Win10 Home all the time, and most ddev windows users do as well. Haven't heard of trouble. And it doesn't require admin privs either.@aszalacinski commented on GitHub (Mar 31, 2020):
I am not getting a failure on mkcert -install but the root ca was not installed into the local Trusted Root Cert Auth; Manually importing the rootCA.pem did the trick. Is there more verbose logging that can be enabled?