When I request a certificate via the new v2 API, the intermediate certificate that is provided along with the certificate contains CRLF at the end of each line. The Fake intermediate certificate via the staging API only contains LF. Is there a valid reason for it?
The CRLF linefeeds should now be fixed. I’ve repurposed Boulder issue 3557 to add a check that will refuse to start the web front end if the configured PEM certificate chains don’t use the correct line endings. This should help prevent this problem from cropping up again in the future.