Page MenuHomePhabricator

[native] Sign device list during QR auth
ClosedPublic

Authored by bartek on May 6 2024, 3:57 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 6:30 PM
Unknown Object (File)
Sat, Dec 21, 6:30 PM
Unknown Object (File)
Sat, Dec 21, 6:30 PM
Unknown Object (File)
Sat, Dec 21, 6:30 PM
Unknown Object (File)
Sat, Dec 21, 6:30 PM
Unknown Object (File)
Sun, Nov 24, 9:44 PM
Unknown Object (File)
Nov 17 2024, 5:38 AM
Unknown Object (File)
Nov 17 2024, 2:40 AM
Subscribers

Details

Summary

Updated the QR Auth flow on primary device to sign the device list update with Olm account before calling the UpdateDeviceList RPC.

Depends on D11899

Test Plan

Performed the QR Auth flow. Then called the GetDeviceListHistoryForUser RPC to check if the signature is present for the latest update.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.May 6 2024, 4:07 AM
bartek added inline comments.
native/qr-code/qr-code-utils.js
73 ↗(On Diff #39838)

Should we somehow call olmAPI instead? Not sure how we're supposed to do it now

kamil added inline comments.
native/qr-code/qr-code-utils.js
67 ↗(On Diff #39838)

worth adding utils function like isPrimary - I guess we'll use it a lot in future

73 ↗(On Diff #39838)

olmAPI was introduced to use code from /lib - here it doesn't make such a difference as this is only native code but I think it is worth using the olmAPI interface everywhere instead of the direct commCoreModule call

This revision is now accepted and ready to land.May 6 2024, 5:12 AM

Use olmAPI instead of commCoreModule

This revision was automatically updated to reflect the committed changes.