Page MenuHomePhabricator

[native] implement accepting `olm` session
ClosedPublic

Authored by kamil on Dec 18 2023, 5:49 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 22, 10:29 PM
Unknown Object (File)
Fri, Nov 8, 5:11 PM
Unknown Object (File)
Oct 17 2024, 11:14 PM
Unknown Object (File)
Oct 17 2024, 11:14 PM
Unknown Object (File)
Oct 17 2024, 11:14 PM
Unknown Object (File)
Oct 17 2024, 11:14 PM
Unknown Object (File)
Oct 17 2024, 11:13 PM
Unknown Object (File)
Oct 15 2024, 1:19 AM
Subscribers

Details

Summary

Code which receive response from Tunnelbroker with session creation request, calls Identity to get Inbound keys and creates session.

Depends on D10379

Test Plan

Call this method and verify result

Diff Detail

Repository
rCOMM Comm
Branch
publish-olm-stack-4
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Dec 18 2023, 6:54 AM
native/utils/crypto-utils.js
63 ↗(On Diff #34794)

Can you split this string so the lines stay to 80 char width?

This diff looks fine in terms of the inbound session creation itself. Wondering what is our approach to handle session creation failure.

native/handlers/peer-to-peer-message-handler.js
20 ↗(On Diff #34794)

Do we have a plan to inform the other peer that we failed to create inbound session? Alternatively is there a mechanism that will prevent them from sending us encrypted messages we won't be able to decrypt?

This revision is now accepted and ready to land.Jan 4 2024, 3:39 AM

make lines 80 char width

native/handlers/peer-to-peer-message-handler.js
20 ↗(On Diff #34794)

yes, it's described in here - that's the place when this client should inform other peers about a failure, ask for a new session and re-send all messages

This revision was automatically updated to reflect the committed changes.