Skip to content

Conversation

@Xentrice
Copy link
Contributor

EncryptionMode byte added to transferred data

EncryptionMode byte added to ByteArray
@Xentrice
Copy link
Contributor Author

Note:
Im using TWN4/B1.62/CCF4.80/PRS1.04
BIX 4.80

Please ensure this is not caused by version mismatch.

Copy link
Owner

@c3rebro c3rebro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gosh. No, it is not reader specific. You are right. it was just missing. Thank you for contributing.

@c3rebro c3rebro merged commit 3086b28 into c3rebro:master Jul 17, 2024
@Xentrice
Copy link
Contributor Author

Interesting, i was using createFile without Problem. Desfire Docs are sparse and hint at this byte only being required with encryption, yet i testet multiple times and it seems the byte is required with and without. I'm not sure, but i guess it's reader firmware stuff.

@Xentrice
Copy link
Contributor Author

with createFile, i only used unencrypted mode tho. maybe the reader adds the byte here and doesn't on writeData, maybe Desfire can handle one and not the other. I'll run some tests and if I find someting interesting, ill let you know!
Thanks for merging, and a big thank you for your work!

c3rebro added a commit that referenced this pull request Jul 17, 2024
@c3rebro
Copy link
Owner

c3rebro commented Jul 17, 2024

Interesting, i was using createFile without Problem. Desfire Docs are sparse and hint at this byte only being required with encryption, yet i testet multiple times and it seems the byte is required with and without. I'm not sure, but i guess it's reader firmware stuff.

No, i responded too quickly because of an old method signature in my test application. There, a encmode byte was given for no reason. i realized this later when reading the reader docs. thus, i deleted my comment.

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.

2 participants