Skip to content

Conversation

@Premeide
Copy link
Contributor

  • Add option for providing custom aaChallenge

@Premeide Premeide force-pushed the main branch 2 times, most recently from a0e6881 to de25144 Compare August 3, 2024 19:26
@AndyQ
Copy link
Owner

AndyQ commented Sep 24, 2024

Hi, Could you explain why this is useful and needed?

@Premeide
Copy link
Contributor Author

Hi, Could you explain why this is useful and needed?

As an extra security feature, our backend now provides a unique active authentication challenge for the NFC reader to sign. By using a custom AA challenge, we ensure that the challenge/response was specifically executed in the session and not replayed. The app then sends the NFCPassportModel.activeAuthenticationSignature to the backend, along with the rest of the chip data. This requires the NFCPassportReader to optionally accept a custom aaChallenge.

This challenge/signature verification ensures that the app user has actually scanned the passport to retrieve the data, preventing the use of stored passport data.

@vpetrusevici
Copy link

Hi, @AndyQ !
It's really important security feature to make passport based authentication without replay attack vulnerability.
Can we merge this PR please?

@ospfranco
Copy link

This has been open for over a year and it's actually quite necessary from a security point of view. Any chance this can be merged soon @AndyQ ?

@AndyQ
Copy link
Owner

AndyQ commented Dec 2, 2025

Yes indeed - it will be merged soon and will be in the next release.

I'll try to get it merged this week so it's in main at least. Next release will hopefully be out by next week.

@ospfranco
Copy link

Awesome! It would be great if #261 can also be merged, current install takes ages as it clones a huge repo

@AndyQ
Copy link
Owner

AndyQ commented Dec 3, 2025

Sure will also look at including that PR too

@AndyQ AndyQ merged commit d37027f into AndyQ:main Dec 10, 2025
AndyQ added a commit that referenced this pull request Dec 10, 2025
…issue #259

Added ability to provide a custom AA Challenge key for supporting backend AA challenges and eliminating replay attacks - PR #227
Updated to use the binary OpenSSL-Package to improve repo loading times and updated Cocoapods to use OpenSSL 3.3.1001 binary too - PR#263 (part)
Updated docs to say that Cocoapods will continue to be released to until end-2026 but will not be a supported deployment. - Issue #262
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