Skip to content

Let's-Encrypt still only supports PKCS#1 1.5 - perl acme clients now fail #146

@rhandom

Description

@rhandom

Recent security updates made use_pkcs1_padding throw this error:

PKCS#1 1.5 is disabled as it is known to be vulnerable to marvin attacks

I believe it is good to have this throw by default.

Let's Encrypt currently only supports PKCS#1 1.5 for its authentication key certificate signing as part of its jwk negotiaion (Not invovled in the creation of actual SSL certs). Any Perl ACME client that uses Crypt::OpenSSL::RSA can now no longer authenticate.

I can't tell you what to do, but I can no longer user Crypt::OpenSSL::RSA for my ACME client.

For my purposes it would be good if there was a way to enable it with sufficient acknowledgement that doing so is insecure.

AI blurb
No, Let's Encrypt does not currently support RSASSA-PSS for Certificate Signing Requests (CSRs) or for signing certificates, according to community discussions. Submitting a CSR with an RSASSA-PSS signature results in an "Internal error" (HTTP 500)

Key Details regarding Let's Encrypt and Key Support:
Supported RSA Keys: Let's Encrypt supports standard RSA keys (2048, 3072, or 4096 bits) and ECDSA keys (P-256 or P-384).
Alternative Support:
While RSASSA-PSS is not supported, you can use standard PKCS#1 v1.5 signatures.
TLS 1.3: RSASSA-PSS certificates are generally rarely permitted or supported in many TLS 1.3 implementations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions