-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
hf mfdes value can't credit/debit value files when communication mode isn't plain #2712
Comments
The added context above is mine. I ran those commands intentionally with the command flags |
This is the result of mismatched default communication modes. |
crediting/debiting with
however when the file is using any other access mode (mac or encrypt), it fails with with mac access mode:
with encrypt/full access mode:
so the problem appears to be in the command's handling of those 2 communication modes |
Describe the bug
the
hf mfdes value
command with-o credit
or-o debit
fails withDesfire ValueFileOperations (0x0c) command ( error ) Result: -20
however, the
hf mfdes write
command (optionally with--debit
) can do so just fineTo Reproduce
Steps to reproduce the behavior:
hf mfdes createapp --aid 000001
hf mfdes createvaluefile --aid 000001 --fid 01 --lower 00000000 --upper 7fffffff --value 00000000
hf mfdes value --aid 000001 --fid 01 -o credit -d 00000001
hf mfdes value --aid 000001 --fid 01 -o get
to see it is still 0hf mfdes write --aid 000001 --fid 01 -d 00000064
hf mfdes value --aid 000001 --fid 01 -o get
to see it was credited successfullyExpected behavior
the value file would be successfully credited/debited by the given value
Screenshots
Desktop (please complete the following information):
OS: Arch Linux
Additional context
confirmed by other members of the discord in the desfire channel
verbose output from the value and write commands:
The text was updated successfully, but these errors were encountered: