mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-26 05:05:56 +03:00
[PR #1074] [CLOSED] fix: disbale cn in csr for specific profile #1131
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#1131
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?
📋 Pull Request Information
Original PR: https://github.com/certimate-go/certimate/pull/1074
Author: @ZeroClover
Created: 12/1/2025
Status: ❌ Closed
Base:
main← Head:fix/disable-cn📝 Commits (1)
6913039fix: disbale cn in csr for specific profile📊 Changes
2 files changed (+8 additions, -0 deletions)
View changed files
📝
cmd/intercmd.go(+4 -0)📝
internal/workflow/engine/executor_bizapply.go(+4 -0)📄 Description
fix https://github.com/certimate-go/certimate/issues/1072
Pass flag to lego to disable CN in CSR when using
tlsserverorshortlivedconfigurationAccording to Let's Encrypt documentation, certificates issued when using these two Profiles do not contain CN, so removing CN from the CSR is also reasonable
Also avoid including IP addresses in CSR CN when issuing IP certificates
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.