fix(transport): Attempt to load RSA private keys in rustls #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, using an RSA key - or indeed any text which is not a PEM-encoded PKCS8-format key with RusTLS panics with an index-out-of- range exception. There is a similar problem loading certificates as well as private keys.
Solution
This commit introduces two new types of
TlsError
which indicate problems with loading a certificate or private key:CertificateParseError
, indicating that the certificate cannot be parsed.PrivateKeyParseError
, indicating that the private key cannot be parsed.Additionally, in the case that reading the private key as PKCS8 fails, we now try loading it as an RSA key before failing.
This is not necessarily a complete solution, since the
Server
builder calls unwrap on the resulting error (which still panics), but the reason is at least now clearer since the variant of theTlsError
is displayed.