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
F3877483: D11293.id37990.diff
Thu, Jan 23, 12:47 PM
F3877479: D11293.id38011.diff
Thu, Jan 23, 12:47 PM
F3877476: D11293.id.diff
Thu, Jan 23, 12:47 PM
F3877395: D11293.id38247.diff
Thu, Jan 23, 12:45 PM
F3877394: D11293.id37984.diff
Thu, Jan 23, 12:45 PM
F3877392: D11293.id38123.diff
Thu, Jan 23, 12:45 PM
F3877373: D11293.id37971.diff
Thu, Jan 23, 12:44 PM
F3876879: D11293.diff
Thu, Jan 23, 12:31 PM
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