chore: Use rustls, remove dependency on OpenSSL #229
Closed
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.
ring 0.17 supports RISC-V, so building Pulsar with rustls instead of OpenSSL is possible.
Choice of the TLS library is exposed by the following features in the
smtp-notifier
crate:native-tls
- uses the native TLS library in the system, usually OpenSSL. Enabled by default.boring-tls
- uses BoringSSL. Disabled by default.rustls-tls
- uses rustls. Disabled by default.When building Pulsar with Cargo, the native TLS is going to be used.
However, for binary builds for Github releases, rustls is being used, since it's always statically built and doesn't require any runtime dependencies from the users.