Element-R: login-and-verify tranche 3: completion #25319
Labels
A-Element-R
Issues affecting the port of Element's crypto layer to Rust
T-Task
Tasks for the team like planning
Build on #24983 and #25316
Implement
CryptoApi.getVerificationRequestsToDeviceInProgress
inRustCrypto
. It just callsOlmMachine::get_verification_requests
and wraps the resultsIntegration test: send an incoming
m.key.verification.request
and check thatgetVerificationRequestsToDeviceInProgress
returns something useful.Estimate: 1d
Element-R: implement
CryptoApi.getVerificationRequestsToDeviceInProgress
matrix-org/matrix-js-sdk#3497Implement
CryptoApi.requestVerificationToDevice
in Rust. It callsOlmMachine::get_identity(my_user_id).request_verification
and sends theOutgoingVerificationRequest
, then wraps the VerificationRequest and returns it.After this, the happy-path integration test we wrote in Element-R: login-and-verify tranche 1: groundwork #24983 should pass.
Estimate: 2d, to get everything working right.
Element-R: Basic implementation of SAS verification matrix-org/matrix-js-sdk#3490
In SetupEncryptionStore (in react-sdk), replace:
Fix access to deprecated methods in
SetupEncryptionStore
matrix-org/matrix-react-sdk#11107After this, the cypress test we wrote in Element-R: login-and-verify tranche 1: groundwork #24983 should pass.
Estimate: another 2d? to get it working reliably.
The text was updated successfully, but these errors were encountered: