FiloSottile/mkcert

CA installation in windows throwing ERROR "ERROR: add cert: Failed adding cert: The request is not supported"

Open

#176 opened on Jul 15, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (3,115 forks)batch import
Windowshelp wanted

Repository metrics

Stars
 (58,912 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi,

Thanks to mkcert for providing us a great tool for multiple environments. Anyone, could you please give me a hint why I am getting the below error. The background is, I have a node js application which is taking help of mkcert to create a CA for Windows. While starting the nodejs app, it ended with the error

(node:2192) UnhandledPromiseRejectionWarning: Error: Command failed: SET CAROOT=C:\Program Files (x86)\Test\cert && "C:\Program Files (x86)\Test\cert\mkcert-v1.3.0-windows-amd64.exe" -install -cert-file "C:\Program Files (x86)\Test\cert\localhost.crt" -key-file "C:\Program Files (x86)\Test\cert\localhost.key" localhost Created a new local CA at "C:\Program Files (x86)\Test\cert" 💥 ERROR: add cert: Failed adding cert: The request is not supported.

Notes:

  • I have customized the CARROT.
  • while looking at the mkcert code, the error is thrown by truststore_windows.go at addCert, which is internally calling crypt32.dll. I am not sure what is going wrong with crypt32.dll . @FiloSottile , could you please have a look at this. Thanks,

Contributor guide

Research direction
Investigate the crypt32.dll AddCertificateToStore call in truststore windows.go. Check if the certificate store is accessible and if the operation requires administrator privileges. Reproduce the issue on a Windows VM with the exact CAROOT path.
Tech stack
go
Domain
securitycli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoWindows
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40