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

Binary characters in output of IDENTIFY #24

Closed
gogobd opened this Issue Oct 10, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@gogobd

gogobd commented Oct 10, 2016

For most of my cards "IDENTIFY" doesn't work, even though I see through logging that there's some "good" information coming in. That works only in reader config, right?

@cons0l3

This comment has been minimized.

Show comment
Hide comment
@cons0l3

cons0l3 Oct 11, 2016

Contributor

I have a "garbled" output before and after CONFIG= and IDENTIFY
in minicom --device /dev/ttyACM0 session:

VERSION?
101:OK WITH TEXT
ChameleonMini RevG 161007 using LUFA 151115 compiled with AVR-GCC 4.9.2
Based on the open-source NFC tool ChameleonMini
https://github.com/emsec/ChameleonMini
commit f46f5b4

CONFIG=ISO14443A READER
_G@ISO14443A READER_100:OK

IDENTIFY
▒t.▒@m▒^zH>t.@.▒v.▒101:OK WITH TEXT
MIFARE Cڱ__ 1▒ .A.▒s.A@.▒t▒6u/=$A
ATQA: 0400
UID: 504DEED2
SAK: 08

Contributor

cons0l3 commented Oct 11, 2016

I have a "garbled" output before and after CONFIG= and IDENTIFY
in minicom --device /dev/ttyACM0 session:

VERSION?
101:OK WITH TEXT
ChameleonMini RevG 161007 using LUFA 151115 compiled with AVR-GCC 4.9.2
Based on the open-source NFC tool ChameleonMini
https://github.com/emsec/ChameleonMini
commit f46f5b4

CONFIG=ISO14443A READER
_G@ISO14443A READER_100:OK

IDENTIFY
▒t.▒@m▒^zH>t.@.▒v.▒101:OK WITH TEXT
MIFARE Cڱ__ 1▒ .A.▒s.A@.▒t▒6u/=$A
ATQA: 0400
UID: 504DEED2
SAK: 08

@gogobd

This comment has been minimized.

Show comment
Hide comment
@gogobd

gogobd Oct 11, 2016

Do you have local logging enabled?

gogobd commented Oct 11, 2016

Do you have local logging enabled?

@cons0l3

This comment has been minimized.

Show comment
Hide comment
@cons0l3

cons0l3 Oct 11, 2016

Contributor

I do not understand your question regarding local logging. I use minicom on linux and enable "local echo" by "Ctrl-A-E". Usually I also activate "line wrap" with Ctrl-A-W. All the commands of minicom can be found in the menu "Ctrl-A-Z"

the rest is just copy&paste ;-)

the "garbled" output of the chameleon looks like uncleared output buffers or a read/write out of memory bounds (fencing issue), because it changes every time I execute it or debug output.

Contributor

cons0l3 commented Oct 11, 2016

I do not understand your question regarding local logging. I use minicom on linux and enable "local echo" by "Ctrl-A-E". Usually I also activate "line wrap" with Ctrl-A-W. All the commands of minicom can be found in the menu "Ctrl-A-Z"

the rest is just copy&paste ;-)

the "garbled" output of the chameleon looks like uncleared output buffers or a read/write out of memory bounds (fencing issue), because it changes every time I execute it or debug output.

@david-oswald

This comment has been minimized.

Show comment
Hide comment
@david-oswald

david-oswald Oct 11, 2016

Collaborator

I think what gogobd means: What is the output of "LOGMODE?" If it is not "OFF", please disable it by sending "LOGMODE=OFF".

The described behaviour is definitely not normal.

Collaborator

david-oswald commented Oct 11, 2016

I think what gogobd means: What is the output of "LOGMODE?" If it is not "OFF", please disable it by sending "LOGMODE=OFF".

The described behaviour is definitely not normal.

@david-oswald david-oswald changed the title from IDENTIFY to Binary characters in output of IDENTIFY Oct 11, 2016

@cons0l3

This comment has been minimized.

Show comment
Hide comment
@cons0l3

cons0l3 Oct 12, 2016

Contributor

Oh, LOGMODE=OFF to the rescue! It was set to LOGMODE=LIVE during my experiments (not that I remember actually setting it). That setting produced the garbled extra bytes during set UID=12345678 and CONFIG=MF_14443A_READER or IDENTIFY!

Wit LOGMODE=OFF the extra bytes are gone.

For the chamtool.py to work properly it assumes LOGMODE=OFF or MEM. It should therefore
a) issue a LOGMODE=OFF when making the connection.
or
b) issue a LOGMODE? if it is LIVE print an error message and exit
or
c) issue a LOGMODE? if it is LIVE set to OFF or MEM

Otherwise it will choke over all "extra" bytes sent by the chameleon, as in my case!

I can make a pull request, what should I implement a), b) or c)?

Contributor

cons0l3 commented Oct 12, 2016

Oh, LOGMODE=OFF to the rescue! It was set to LOGMODE=LIVE during my experiments (not that I remember actually setting it). That setting produced the garbled extra bytes during set UID=12345678 and CONFIG=MF_14443A_READER or IDENTIFY!

Wit LOGMODE=OFF the extra bytes are gone.

For the chamtool.py to work properly it assumes LOGMODE=OFF or MEM. It should therefore
a) issue a LOGMODE=OFF when making the connection.
or
b) issue a LOGMODE? if it is LIVE print an error message and exit
or
c) issue a LOGMODE? if it is LIVE set to OFF or MEM

Otherwise it will choke over all "extra" bytes sent by the chameleon, as in my case!

I can make a pull request, what should I implement a), b) or c)?

@cons0l3

This comment has been minimized.

Show comment
Hide comment
@cons0l3

cons0l3 Oct 19, 2016

Contributor

should a implement any of the options a)-c) above and sent you a pull request?

Contributor

cons0l3 commented Oct 19, 2016

should a implement any of the options a)-c) above and sent you a pull request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment