Proxmark3 community

T.

Contributor

Registered: 2017-09-20

Posts: 20

Problem chk

Dear All,

I am using on a mifare 1k classic :

hf mf 1 0 A ffffffffffff

That provides me with two new keys :
(E9a3cc4bd132 and 7b5dc26aa41e)

-----------------------------------------------
Nested statistic:
Iterations count: 32
Time in nested: 41.660 (1.302 sec per key)
|---|----------------|---|----------------|---|
|sec|key A           |res|key B           |res|
|---|----------------|---|----------------|---|
|000|  240025002600  | 1 |  ffffffffffff  | 1 |
|001|  240025002600  | 1 |  ffffffffffff  | 1 |
|002|  240025002600  | 1 |  ffffffffffff  | 1 |
|003|  240025002600  | 1 |  ffffffffffff  | 1 |
|004|  240025002600  | 1 |  ffffffffffff  | 1 |
|005|  240025002600  | 1 |  ffffffffffff  | 1 |
|006|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|007|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|008|  e9a3cc4bd132  | 1 |  7b5dc26aa41e  | 1 |
|009|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|010|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|011|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|012|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|013|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|014|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|015|  ffffffffffff  | 1 |  ffffffffffff  | 1 |
|---|----------------|---|----------------|---|
Printing keys to binary file dumpkeys.bin...

I then try to use them to read the blocks in question and it work.
But when I am using chk

proxmark3> hf mf chk *1 ?

I get

|---|----------------|---|----------------|---|
|sec|key A           |res|key B           |res|
|---|----------------|---|----------------|---|
|000|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|001|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|002|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|003|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|004|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|005|  00000000fb25  | 1 |  ffffffffffff  | 0 |
|006|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|007|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|008|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|009|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|010|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|011|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|012|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|013|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|014|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|015|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|---|----------------|---|----------------|---|

ok, and when I provide

proxmark3> hf mf chk *1 ? e9a3cc4bd132  7b5dc26aa41e 

--chk keys. sectors:16, block no:  0, key type:B, eml:n, dmp=n checktimeout=471 us
chk key[ 0] e9a3cc4bd132
chk key[ 1] 7b5dc26aa41e

To cancel this operation press the button on the proxmark...
--.
No valid keys found.

proxmark3>

Why is that ? so I cannot crack the card and dump all the keys unfortunately.

Thank you

piwi

Contributor

Registered: 2013-06-04

Posts: 704

Re: Problem chk

Inconsistencies like these are usually the result of mixing client software (on your PC) and firmware (on Proxmark) from different repositories or different releases.