AESCipher decrypt error #31
Assignees
Comments
|
Can you test if it makes any difference changing aes key length to Also word of advice, you're logging on the finest level which might leak sensitive data. |
|
Hi, I have tried it already, but am getting another error: ive tried hardcoding the blocksize in pointycastle to set the make but its weird because |
|
Hi I have seemed to fix the above error by changing some parts in the pointycastle package. It seems to work on Android well. |
|
Looking at your second log, I see that AES128 was selected. This happens here: Line 547 in 8ced760 Did you try changing the key size to 256 (KEY_LENGTH.s256)?
Do you get any specific log entry when app gets stuck? |
|
Hi yes, i have tried changing it to I changed it to and it now manages to work. |
|
Looking at pointycastle code that you linked it's definitively wrong IV size for block cipher modes. |
|
Thanks for the info, I have fixed the ios error, it had to do with permissions for the NFC to work: https://stackoverflow.com/questions/56453525/missing-required-entitlement-for-nfctagreadersession |
|
Just to be clear, you had to add nfc entitlement to the iso project, is that right (like the example app)? |
|
Yes, and I also had to add the following: |
|
Ah yes the |
|
Just browsing what this lib might be able to do and what kind of issues are encountered, and the need to specify these AIDs sounded interesting to make it work... so I searched and found https://www.eftlab.com/knowledge-base/complete-list-of-application-identifiers-aid which seems to provide descriptions for two of the AID entries mentioned; the all zeroes wasn't on there as such. Not sure if it helps in this area, complete N00b here ;-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am getting an error when using this package on PACE-enabled passports.
The following shows the error logs:
It works fine for BAC though
The text was updated successfully, but these errors were encountered: