4 ms·
Normally, a user identity in an end to end encrypted messaging system ultimately takes the form of a ridiculously long number. From the SimpleX white paper: >S
by upofadown 3y ago
Normally, a user identity in an end to end encrypted messaging system ultimately takes the form of a ridiculously long number. From the SimpleX white paper:
>SMP is initialized with an in-person or out-of-band introduction message, where Alice provides Bob with details of a server (including IP, port, and hash of the long-lived offline certificate), a queue ID, and Alice's public key for her receiving queue.
So the identity here is the ridiculously long number formed from "Alice's public key for her receiving queue" combined with all that other stuff, isn't it? In other words, a user ID?
Would it perhaps be more accurate to describe this as a system with separate user IDs for each contact?
- runeks 3y ago> So the identity here is the ridiculously long number formed from "Alice's public key for her receiving queue" combined with all that other stuff, isn't it? In other words, a user ID? If Alice's public key is an ephemeral key used only for a single connection -- as with e.g. HTTPS -- then it can't meaningfully be called a "user ID". Then it really is just a random number negotiated as part of making the connection and thrown away when the connection is terminated.
- SpaghettiCthulu 3y agoI think that would be an accurate description of the system.