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
Details
Details
TBD
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| 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 |
| 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? |
| 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. |