-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key exchange update #35
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better, but needs some some more work to be entirely clear.
|
||
Below is the 3-party ECDH protocol between $S$, $P$ and $V$, enabling $P$ and $V$ to arrive at shares of $\mathbb{pms}$. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Below is the 3-party ECDH protocol between $S$, $P$ and $V$, enabling $P$ and $V$ to arrive at shares of $\mathbb{pms}$. | |
$S$, $P$ and $V$ perform the 3-party ECDH protocol together. The result is that both $P$ and $V$, each have a share of the $\mathbb{pms}$. The 3-party ECDH protocol consists of following steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like we should avoid 3-party here. I'd say the server plays its normal role. The TLS-client is a 2PC between the Prover and the Verifier.
Note that the diagram also uses 2PC
|
||
Below is the 3-party ECDH protocol between $S$, $P$ and $V$, enabling $P$ and $V$ to arrive at shares of $\mathbb{pms}$. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we mention that the notation is from Wikipedia, so ppl could have wikipedia open and easier follow the explanation.
|
||
|
||
1. $S$ sends its public key $Q_b$ to $P$, and $P$ forwards it to $V$ | ||
2. $P$ picks a random private key share $d_c$ and computes a public key share $Q_c = d_c * G$ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change the diagram to also have the word "share" there?
This PR updates our key exchange section