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

Handling error cases if the key is parsed but is not valid. #241

Merged

Conversation

jaredwolff
Copy link
Contributor

The cause can be something as simple as not having RSA in -----BEGIN RSA PRIVATE KEY-----. It applies both to the client
and server side. Mentioned this in #236

The cause can be something as simple as not having RSA in -----BEGIN RSA PRIVATE KEY-----. It applies both to the client
and server side.
@tekjar tekjar merged commit 355fa53 into bytebeamio:master Jan 28, 2021
@tekjar
Copy link
Contributor

tekjar commented Jan 28, 2021

Thanks!! :)

@jaredwolff jaredwolff deleted the invalid-key-error-if-fail-to-parse branch January 28, 2021 18:24
carlocorradini pushed a commit to carlocorradini/rumqtt that referenced this pull request Aug 3, 2023
…io#241)

The cause can be something as simple as not having RSA in -----BEGIN RSA PRIVATE KEY-----. It applies both to the client
and server side.
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

Successfully merging this pull request may close these issues.

2 participants