[PR #89] [CLOSED] Add support for client certificates #387

New issue

Closed

opened 2026-02-25 22:33:21 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 22:33:21 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/FiloSottile/mkcert/pull/89
Author: @jtdowney
Created: 11/2/2018
Status: ❌ Closed

Base: master ← Head: client-certificate-support

📝 Commits (1)

ea290a6 Add support for client certificates

📊 Changes

2 files changed (+14 additions, -2 deletions)

View changed files

📝 cert.go (+8 -1)
📝 main.go (+6 -1)

📄 Description

This change adds a new flag for client certificates. When this flag is passed, the extended key usage for the generated certificate is for client authentication instead of server authentication.

I am not 100% sure this is a good idea, but I found myself needing to generate both server and client certificates for a project and thought that mkcert could fit both of those cases.

The change was remarkably easy to make so I figured I'd submit a PR.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/FiloSottile/mkcert/pull/89 **Author:** [@jtdowney](https://github.com/jtdowney) **Created:** 11/2/2018 **Status:** ❌ Closed **Base:** `master` ← **Head:** `client-certificate-support` --- ### 📝 Commits (1) - [`ea290a6`](https://github.com/FiloSottile/mkcert/commit/ea290a629b22ee9331151cfb92b945355f8ecba1) Add support for client certificates ### 📊 Changes **2 files changed** (+14 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `cert.go` (+8 -1) 📝 `main.go` (+6 -1) </details> ### 📄 Description This change adds a new flag for client certificates. When this flag is passed, the extended key usage for the generated certificate is for client authentication instead of server authentication. I am not 100% sure this is a good idea, but I found myself needing to generate both server and client certificates for a project and thought that `mkcert` could fit both of those cases. The change was remarkably easy to make so I figured I'd submit a PR. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>