handle RSA_R_KEY_SIZE_TOO_SMALL error

[anonrig]

No description provided.

[ask-bonk]

I've now reviewed the full context of both changed files. Let me analyze:

Changes summary:

1. impl.c++: Adds RSA_R_KEY_SIZE_TOO_SMALL error mapping in two places — throwOpensslError() (via MAP_ERROR macro) and consumeAllOpensslErrors() (via direct case statement). Both map to "RSA key size is too small.".
2. impl-test.c++: Adds a test verifying the new error is converted to a DOMException(OperationError) instead of an internal error.

Review analysis:

• The change converts what was previously an internal/opaque BoringSSL error into a user-facing DOMOperationError. This is a behavior change (the error message and exception type change), but it's strictly an improvement: the error was already thrown, just with an unhelpful internal message. Converting it to a clearer user-facing message does not break backward compatibility since no reasonable code would depend on the specific internal OpenSSL error string format.
• Both code paths (throwOpensslError and consumeAllOpensslErrors) are updated consistently with the same error string.
• The test is well-structured, following the existing test pattern exactly.
• No security concerns — this only changes error message text, not control flow.
• No compat flag needed — this is an error path improvement that makes errors more user-friendly and reduces Sentry noise.
• No memory safety issues.

This is a clean, minimal, well-tested change. No actionable issues.

LGTM

github run