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

Add a blind signatures extension #73

Closed
wants to merge 1 commit into from

Conversation

sev71
Copy link

@sev71 sev71 commented May 3, 2020

Add a blind signatures extension to address the possible collusion between backend and authority (tries to solve the issue DP-3T/documents#210).

Tried to adapt your code and naming style.

Only tested with the dev config and HSQLDB.

The authority controller test shows the protocol workflow.

If there is enough interest, I could complete the feature.

@wouterl
Copy link

wouterl commented May 5, 2020

I don't think we should use blind signatures for now. Given the timescale, we prefer to use standardized cryptography as much as possible.

There is indeed a residual risk of the health authority colluding with the backend. However, using blind signatures alone will not solve that risk. In the current system, the app interacts with the health backend and then immediately after with the backend you see here. To prevent collusion attacks, implementations need to also hide IP addresses and time correlations. Both of which are very hard to do.

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.

None yet

3 participants