-
Notifications
You must be signed in to change notification settings - Fork 56
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 support for active authentication #62
Comments
How can we identify a passport holder exectly own this passport? Can we authenticate the public key of the passport holder in chip by using active authentication? |
Hi, |
OK, thank you |
Just found another problem about the active authentication. The length of the challenge to be signed is just 8 bytes which is not enough for most use cases. Do you have any idea about this problem? |
Hi |
I think the problem is that an attacker may be able to combine four signatures for 8 bytes. And then pass all the signatures verification step. |
Very interesting question. My guess is the following:
|
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI have developed lots of systems that had to handle safety, authorization and authentication taking into account the structure and dynamics of the system and how it's used. How I plan on tackling this issueThe approach would depend on what works with the original user experience but solves the problem, which as of yet I have not determined |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedElectrical engineer with 3 years using c++ How I plan on tackling this issueCircom and using active verification |
Right now, we only use passive authentication by checking the passive attestation placed by country signing authorities in the SOD file. This has a drawback: it's possible for an attacker to copy the data and generate a proof of passport without physically owning the passport anymore.
We want to support active auth and/or chip auth. See country coverage here.
The active auth pubkey is in the DG15 of the SOD file which can be easily checked like the DG1 is currently.
The FreedomTool team has worked on this in circom.
It's apparently also been done in Noir by Michael here.
See here too.
The text was updated successfully, but these errors were encountered: