FiloSottile/mkcert

IIS complains about missing intermediates

Open

#148 opened on Mar 13, 2019

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

Description

Hi,

  • Windows 10 1809 Professional
  • IIS 10.0.17763.1
  • Have run mkcert -install

Generated my new wildcard certificate as:

 mkcert -pkcs12 "*.ozc.black"

I then go to IIS > Server Certificates and try and import it but am prompted for a password?

image

What am I missing here? It is not my login password.

Contributor guide

Tech stack
go
Domain
clideveloper experiencesecurity
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Go knowledgeUnderstanding of PKCS12 formatIIS certificate import experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate mkcert's PKCS12 generation in pkg/pkcs12.go to determine if a password is set by default. Check if IIS expects a non empty password; the standard PKCS12 password is often empty. Update the code to allow a user specified password via a flag, or document that the default empty password can be used. Test importing the generated PKCS12 file with an empty password in IIS to verify.