-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bump ureq to 3.0.0 #35
base: main
Are you sure you want to change the base?
Conversation
And it would also make the TLS configuration for the tests much easier, so I’m in favor of updating. |
No it would not, on the opposite it would make it more complex. This currently fails because when disabling TLS it says to the server that it does not support any Signature scheme which leads to an error :( And in the pkcs11 module we would still need some custom TLS config. But at least now it will not depend on a semver hazard. |
0cf5f3a
to
09fdb6d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIS the custom Verifier
in the tests can now be removed (and maybe even the rustls
dependency?). And do we still need to pin the ureq
dev dependency to a specific version?
352187d
to
24b81dc
Compare
24b81dc
to
8a0913b
Compare
This would be a breaking change. Benefits: some of the feature we needed to improve the reliability of the pkcs11 module were only available in our fork. This would allow us to use the upstream version.