Milestone: securely transfer Noise sessions

[s1fr0]

Problem

At the end of a successful Noise handshake, each party will compute on their respective device some cryptographic material which is used to secure their future communications. Since the encryption keys will be stored on the devices that executed the handshake, the communication could happen only between such devices.

Scope

With the final goal to implement multi-devices communications, we need to design a mechanism to securely exchange (cryptographic) information between 2 or more devices possessed by a user.

List of issues:

• Design secure information transfer among a user's devices vacp2p/research#130. Solution to this issue required specifically addressing Efficient encrypted message identification #1081 on which depends Analysis for frequent contentTopicchanges in the implementation of Noise session vacp2p/research#131
• Propose an RFC: New RFC: 43/WAKU2-NOISE-PAIRING vacp2p/rfc#531
• Implement the design agreed in previous point PoC implementation of Waku Pairing and Secure Transfer #1117

Acceptance criteria

Issues defined in scope addressed.

Out of scope

Synced multi-device n-to-m communications between Alice and Bob.

[oskarth]

I take this milestone as being something you are working on right now @s1fr0