Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Done
-
None
-
None
-
Debian 10
-
Froyo
-
1
-
Froyo - 1/19/2022
-
Customer Feedback
-
Bug Fix
-
-
Needs Assessment
Description
Hello,
Following PA-3979, I found a weird puppet behavior during CA certificate generation.
When generating the CA crt with "puppetserver start", "Authority Key Identifier" is set in the CA crt with the issuer :
X509v3 Authority Key Identifier:
|
DirName:/CN=Puppet CA: puppet
|
serial:01
|
If I regenerate the CA crt with pupperserver ca setup, this field is filled with a keyid :
X509v3 Authority Key Identifier:
|
keyid:04:27:BC:E8:9A:D9:15:9F:3F:1A:0F:F0:0D:71:99:65:60:CD:AE:75
|
The issue is that LibreSSL get in trouble with the first one and cannot validate any certificate with it.
Why the behavior is different between the two ways of generation ?
Thanks in advance
To make Puppet Server generate certs with a keyid instead of a DirName:
Attachments
Issue Links
- relates to
-
SERVER-2338 PuppetCA should issue certs with Subject Alternative Name containing the CN for compliance with RFC 2818
-
- Resolved
-