Skip to content
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

"DETECTION" Support Missing for mfkeys32 Attack #13

Closed
digitalentropy opened this issue Mar 10, 2020 · 10 comments
Closed

"DETECTION" Support Missing for mfkeys32 Attack #13

digitalentropy opened this issue Mar 10, 2020 · 10 comments

Comments

@digitalentropy
Copy link

digitalentropy commented Mar 10, 2020

On Latest RRG firmware (2020-02-03) DETECTION command appears to be missing from "HELP", breaking mfkeys32 functionality in the Windows GUI.

Log output from GUI:

[=] Connecting to USB Serial Device (COM13) at COM13
[!] Firmware doesn't support DETECTION cmd -- mfkey32 key recovery is not possible
[+] Success, found Chameleon Mini device on 'COM13' with Firmware RevG Official installed
@digitalentropy digitalentropy changed the title "DETECT" Support Missing for mfkeys32 Attack "DETECTION" Support Missing for mfkeys32 Attack Mar 10, 2020
@iceman1001
Copy link
Collaborator

The bug is most likely here.
https://github.com/RfidResearchGroup/ChameleonMini/blob/proxgrind/Firmware/Chameleon-Mini/Terminal/CommandLine.c#L334

The three extra commands is added after the supposed "last item" object.

@tssmcu
Copy link

tssmcu commented Mar 11, 2020

Actually, Willok upgrade the DETECTION function, The new mfkey32 is powerful than before.
The new mfkey32 V2 can continuously record hundreds of traces, So we changed the way of communication and the data structure. New DETECTION(mfkey32v2) need to use Xmodem to download LOG file. then calculate mfkey32v2 with the log data.
Here is the DETECTION log data format in the attach.
REV.G_Detection(Mfkey32V2)_Log_format_explain.pdf

@tssmcu
Copy link

tssmcu commented Mar 11, 2020

Hope the GUI can support new mfkey32 soon :)

@iceman1001
Copy link
Collaborator

That link doesn't work.

In order for cross application interaction to work, we need documentation over what has been done, how to use. When you make breaking changes like that, don't expect anything to work with other applications.

GUI most likely will not be updated for some time.

@tssmcu
Copy link

tssmcu commented Mar 11, 2020

I know, Try again, the link should work now.

@iceman1001
Copy link
Collaborator

Link works. Doesn't solve this issue.
So this issue needs to be addressed.

@db69
Copy link

db69 commented Mar 11, 2020

Can we have MFkey32V2 without calling home through XMODEM; we do not want our keys to be collected by 3rd parties ! Had the same issue with RFIDTools.
Logfile can be loaded in memory, and we will need to use the Chameleon in places without network access

@tssmcu
Copy link

tssmcu commented Mar 12, 2020

I think you misunderstood our APP,The both of the APP does not need network at all.
They all run completely offline.
And yes, the Logfile is saved in memory.
XMODEM is a UART based communication protocol. It's nothing to do with network.
the XMODEM protocol used to transmit large amounts of data,like dump file.
Hope you enjoy :)

@db69
Copy link

db69 commented Mar 12, 2020 via email

@Ziglar1
Copy link

Ziglar1 commented Sep 2, 2020

the 2020-07-14 firmware supports the original question.
2020-07-14_Chameleon.zip

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

No branches or pull requests

5 participants