Page MenuHomePhabricator

[lib] Add Tunnelbroker message types for QR code auth
ClosedPublic

Authored by bartek on Mar 11 2024, 6:17 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 25, 8:10 AM
Unknown Object (File)
Thu, Apr 25, 8:10 AM
Unknown Object (File)
Thu, Apr 25, 8:10 AM
Unknown Object (File)
Thu, Apr 25, 8:10 AM
Unknown Object (File)
Thu, Apr 25, 8:06 AM
Unknown Object (File)
Thu, Apr 25, 7:23 AM
Unknown Object (File)
Mar 25 2024, 9:28 PM
Unknown Object (File)
Mar 25 2024, 1:03 AM
Subscribers

Details

Summary

Added a new peer-to-peer message type for QR code auth flow. All messages are going to be encrypted separately via AES-256.

Depends on D11292

Test Plan

TBD

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Mar 12 2024, 1:37 AM
bartek added inline comments.
lib/utils/qr-code-auth.js
13 ↗(On Diff #37984)

Messages are going to be encrypted using AES-256. This is going to be implemented in a further diff. For now it's just stub - the content is JSON-stringified in plaintext

kamil added inline comments.
lib/types/tunnelbroker/peer-to-peer-message-types.js
60–63 ↗(On Diff #38011)

are you sure, you don't need a senderInfo here? How do you plan to decrypt encryptedContent / establish session?

This revision is now accepted and ready to land.Mar 13 2024, 5:35 AM
lib/types/tunnelbroker/peer-to-peer-message-types.js
60–63 ↗(On Diff #38011)

I haven't looked too closely at this code, but let me know if there's any way I can help clarify the protocol

lib/types/tunnelbroker/peer-to-peer-message-types.js
60–63 ↗(On Diff #38011)

Messages are AES-256 encrypted. The encryption key is a part of the QR code. So both parties can encrypt/decrypt.

Add backupLogDataKey to the backup message