Skip to content
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

new keyshare protocol (keyshare server parts) #240

Merged
merged 45 commits into from
Sep 27, 2023
Merged

Conversation

synaptic-cleft
Copy link
Contributor

@synaptic-cleft synaptic-cleft commented Sep 1, 2022

Client implementation follows in #327.

Maja Reissner and others added 30 commits September 1, 2022 16:59
…_0^secret) prior to issuance. This is needed for the client to calculate the hash h_w.
Implement /getPs endpoint for new keyshare protocol
# Conflicts:
#	server/keyshare/keyshareserver/server.go
#	server/keyshare/keyshareserver/server_test.go
…ably secure keyshare protocol.

The upgrade includes breaking changes in both the keyshare server and the app client. Since this pull request will only update the keyshare server, the client code is not upgraded properly here but merely so that it compiles again.
…l builder. Accidently committed the placeholder earlier.
This version of gabi produces a proofU that contains both keyshares. This commit changes the following:
- irmaclient.Client.startKeyshareSession() is now called newKeyshareSession, because it does not actually immediately start the session. Instead, it returns after checking the user's PIN. This is necessary because what happens next now differs per session type, see next point.
- In case of disclosure/ABS, the session proceeds as before. In case of issuance, /api/v2/prove/getPs at the keyshare server is first invoked to retrieve the P values (R_0^{keyshare server secret}), after which the session is started.
- In case of the old keyshare protocol, the keyshare's P is divided out from the U of the proofU because that is what the issuer expects in the old keyshare protocol.
Support gabi with updated keyshare protocol
Keyshare server getResponse v2 endpoints
messages.go Show resolved Hide resolved
@ivard ivard changed the title new keyshare protocol new keyshare protocol (keyshare server parts) Sep 5, 2023
@ivard ivard marked this pull request as ready for review September 5, 2023 09:38
ivard
ivard previously approved these changes Sep 5, 2023
ivard
ivard previously approved these changes Sep 5, 2023
@ivard ivard marked this pull request as draft September 7, 2023 09:41
@ivard ivard marked this pull request as ready for review September 20, 2023 13:54
@ivard ivard enabled auto-merge September 27, 2023 14:25
@ivard ivard merged commit 6fb15fa into master Sep 27, 2023
17 checks passed
@ivard ivard deleted the new-keyshare-protocol branch September 27, 2023 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants