-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
[enhancement]: update rustls dependency to one requiring ring 0.17 #416
Comments
Hi, Stalwart already uses ring version |
thanks @mdecimus , from my reading of inejge/ldap3#117 it seems to be mostly a matter of having a release of |
ah and sorry for the initial wrong first comment, we 'need' ring 0.17 because ring 0.16's assembly (from boringssl) isnt compatible with execute-only and missing landing pads for CFI which is a security feature |
I just executed cargo tree and there three multiple dependencies still linking
Here is cargo tree's output:
|
why was this issue closed ? i see nothing changed wrt the transitive dependencies on ring 0.16.. |
Stalwart is already using ring |
just for tracking purposes so that i don't have to look again:
|
Which feature or improvement would you like to request?
I'd like to see this feature: On OpenBSD, ring crate has proper support for libressl for various architectures only in version 0.17. For now, stalwart-mail requires several versions of ring via several versions of rustls, but support for ring 0.17 was added to rustls in https://github.com/rustls/rustls/releases/tag/v%2F0.21.8
im not fully grasping the dependency trees of cargo ecosystem, but is it possible to upgrade some dependencies so that we can only use/require ring 0.17 in the end ?
Is your feature request related to a problem?
I'm having a problem with...
Code of Conduct
The text was updated successfully, but these errors were encountered: