-
Notifications
You must be signed in to change notification settings - Fork 230
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
SIGSEGV in recovery #77
Comments
did you try to compile and run this forked version: https://github.com/DrSchottky/mfcuk? maybe it would work better .. |
Just tried out. Crashes at exact same position |
@tacticalDevC what about the windows version ? Could you try it ? I have compiled a bunch of tools, available here: http://legacy.averbouch.biz/libnfc-and-nfc-utils-binaries-on-windows-10/#alltools |
I'm sorry I don't have any Windows machine anymore. Let's focus on the code. What do you need to find the error? |
@tacticalDevC you don’t have a dump of this tag so I could test it on my side ? |
@tacticalDevC unfortunately I need a tag dump to try to reproduce this error. |
mfoc doesn't work either. Pls see this issue (spoiler: no one has answered yet). |
@tacticalDevC i replied here: nfc-tools/mfoc#77 |
This is caused by the fact that your card is not a compatible Mifare card (only Classic 1K & 4K are supported AFAIK). I tried the tool with a DESFire v3 and got the same issue. Using it with a real Classic card on the other hand worked for me. |
So I got that SmartMX card with 4k emulation and tried to run the release version 0.3.8
Standard command
./mfcuk -C -R -1
throws a segfault.Time to start gdb... This is the output:
It seems like the program crashes at the verification of the keys.
The funny thing is that if the type parameter is given. It tries to authenticate but constantly throws error 0x08
The card OS is "atrust-acos"
The text was updated successfully, but these errors were encountered: