-
-
Notifications
You must be signed in to change notification settings - Fork 607
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
Remove deprecated parameters and types in CryptoApi
#4670
base: florianduros/rip-out-legacy-crypto/remove-legacy-crypto
Are you sure you want to change the base?
Remove deprecated parameters and types in CryptoApi
#4670
Conversation
CryptoApi
CryptoApi
2693c9c
to
644185d
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.
I'm a bit nervous about this: it goes quite a long way beyond "remove legacy crypto", imho. For example findVerificationRequestDMInProgress
and storeSessionBackupPrivateKey
work ok in rust crypto.
Not saying we shouldn't plan to remove them, but I don't think we should do it as part of this change.
Removing the old DecryptionFailureCode
s and CryptoCallbacks
seems sensible.
Also, the tests are failing.
The legacy crypto tests are failing because of #4659. If we plan to remove them, should be in the same release than the removal of the legacy crypto in order to avoir too many releases with breaking changes. Or do we want to do in some weeks/month? |
I'm not really sure yet. Right now, I'm mostly nervous that we're making sweeping changes without effective CI. To be honest, I think we should leave it for a release or two; maybe get a working Either way: not part of this PR, please? |
I move it back to draft, we will resuscitate it if we need it later |
Remove deprecated parameters in
CryptoApi
and update rust-crypto .