raed667 / encryptedwebrtchatter Goto Github PK

A p2p identity system should be implemented. This system should associate a publicKey with a username.

When a new connection is established, the users exchange and store both publicKeys and usernames.

A user should be able to generate a new identity when starting a new conversation.

If a user receives a public key with a username that he already has stored, we compare the public keys and display a warning if they don't match.

In order to facilitate the exchange of the offer and answer, we should implement a simple PHP + SQLITE server that manages the transfer in a transparent way.

The development of this feature should be managed on a dedicated branch.

could you please document the crypto? it's important to know what security properties you are claiming to provide.

I saw this, which seems significant:
https://github.com/RaedsLab/EncryptedWebRTChatter/blob/master/js/serverless-webrtc.js#L9

I'm just reading between the lines here, but I'm guessing that the intention is this relies on webrtc's own encryption, but you provide your own key negioation, which is part of the thing pasted between sessions?

Is it still forward secure?
is it man in the middleable, etc?