[GH-ISSUE #301] Overly strict checking of CSR header #192

Closed
opened 2026-02-25 22:32:50 +03:00 by kerem · 0 comments
Owner

Originally created by @simo-11 on GitHub (Oct 9, 2020).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/301

Making cert fails for WebSphere initiated request as it has
-----BEGIN NEW CERTIFICATE REQUEST-----
instead of
-----BEGIN CERTIFICATE REQUEST-----
ERROR: failed to read the CSR: expected CERTIFICATE REQUEST, got NEW CERTIFICATE REQUEST
Issue can be bypassed by editing CSR using editor

Originally created by @simo-11 on GitHub (Oct 9, 2020). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/301 Making cert fails for WebSphere initiated request as it has -----BEGIN NEW CERTIFICATE REQUEST----- instead of -----BEGIN CERTIFICATE REQUEST----- ERROR: failed to read the CSR: expected CERTIFICATE REQUEST, got NEW CERTIFICATE REQUEST Issue can be bypassed by editing CSR using editor
kerem closed this issue 2026-02-25 22:32:50 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mkcert#192
No description provided.