Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation with external CA produces a CSR with legacy header that is unrecognized by python-cryptography 35 #3843

Closed
flo-renaud opened this issue Nov 15, 2021 · 1 comment
Assignees

Comments

@flo-renaud
Copy link

IPA server installation with an external CA is done in a 2-step process, the first step produces a CSR that needs to be signed by the external CA.
The CSR produced by PKI is unrecognized by python-cryptography 35 (shipped in fedora rawhide) because it contains a header BEGIN NEW CERTIFICATE REQUEST instead of BEGIN CERTIFICATE REQUEST. pkispawn should produce a CSR with the most recent format (the NEW is still acceptable but generators should not be doing it per https://datatracker.ietf.org/doc/html/rfc7468#section-7):

   The label "NEW CERTIFICATE REQUEST" is also in wide use.  Generators
   conforming to this document MUST generate "CERTIFICATE REQUEST"
   labels.  Parsers MAY treat "NEW CERTIFICATE REQUEST" as equivalent to
   "CERTIFICATE REQUEST".

See the code in

# add header and footer
with open(request_file, 'w') as f:
f.write('-----BEGIN NEW CERTIFICATE REQUEST-----\n')
f.write(b64_request)
f.write('-----END NEW CERTIFICATE REQUEST-----\n')
.

@edewata
Copy link
Contributor

edewata commented May 25, 2023

This issue has been fixed in the master branch (PKI 11.5).

@edewata edewata closed this as completed May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants