Adding a function to verify QR signature #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also, adding some better error handling and debugging print statements.
From Secure QR documentation (User_manulal_QR_Code_15032019.pdf):
Validate (signature value and signed data value) by using public key with algorithm SHA256withRSA.
The default public key is "pyaadhaar/uidai_publickey.pem", which is extracted from the certificate
present in the offline KYC XML (uidai_certificate_from_xml.cer).
> openssl x509 -inform PEM -in uidai_certificate_from_xml.cer -pubkey -noout > uidai_publickey.pem
…tatus field. 3 and 2 have email. 3 and 1 have mobile. Also, using the isEmailRegistered() and isMobileNoRegistered() functions, instead of checking the email_mobile_status field everywhere.
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In addition to the verification function, added some error-handling code.