mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #42] Windows Support #21
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#21
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 @klauern on GitHub (Jul 7, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/42
I know it's mentioned in the README that this support is coming soon, but I'd like to correlate it to an issue that can be tracked. :)
@sebdeckers commented on GitHub (Jul 11, 2018):
Here is the Windows solution to entrust certificates in the OS store:
https://gitlab.com/sebdeckers/tls-keygen/blob/master/index.js#L202-224
Should be easy for someone to port this over to Golang.
Just found out about mkcert. Half a year ago I implemented a similar tool using Node.js for Mac/Lin/Win.
🗝
tls-keygen@cretz commented on GitHub (Jul 11, 2018):
Alternatively you can use
crypt32.dll, see this reference. Specifically, you can probably call CertAddEncodedCertificateToSystemStoreA with "ROOT" and the raw cert bytes (ASN I would guess).Edit: I'll probably just make a PR for this functionality
@cretz commented on GitHub (Jul 11, 2018):
Done, ref #46. I signed the CLA too.
@JacobDB commented on GitHub (Jul 17, 2018):
Having this work with WSL, and not just CMD would be awesome. Not sure how that would work interfacing between the Linux environment and Windows though.
@adamdecaf commented on GitHub (Jul 17, 2018):
Doesn't WSL (with Ubuntu) use the Ubuntu certificate store filepath? IIRC there was nothing windows specific when I tried it.
@cretz commented on GitHub (Jul 17, 2018):
It all comes down to how it's compiled. If it's compiled with Linux Go in WSL, when run it will do the Linux thing. If it's compiled with Windows Go, it will do the Windows thing. Do in theory, due to the fact that WSL can execute Windows
.exes, you can download/have twomkcertexecutables callable in WSL, one that does a Linux thing and one that does a Windows thing :-)Note, it does not appear that WSL and Windows share root stores. There is this question out there: https://github.com/Microsoft/WSL/issues/3161
@Geczy commented on GitHub (Jul 29, 2018):
Any updaet
@2PintChristianN commented on GitHub (Sep 9, 2025):
Noticed that the binary is not signed on windows, which makes windows defender less than happy :/ Borderline bug in our situation.