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

clone card #139

Closed
c64bob opened this issue Jul 12, 2017 · 7 comments
Closed

clone card #139

c64bob opened this issue Jul 12, 2017 · 7 comments

Comments

@c64bob
Copy link

c64bob commented Jul 12, 2017

Sorry for what is probably a noob question: I'm trying to clone a Mifare Classic 1k Card, writing only block 0 to a special tag. Most of the dump is being written successfully, but the keys (A & B) from the dump aren't written to the new tag. Shouldn't they be written as well when cloning a tag?

@ikarus23
Copy link
Owner

Hi @c64bob,
yes, by using the clone function as much as possible should be written. this includes the keys. However, maybe the tag you want to write on has access conditions that prevent writing the keys.

Can you post the third block (keys & access conditions) of a sector of the target block where the writing fails?

@c64bob
Copy link
Author

c64bob commented Jul 12, 2017

Sure:

FFFFFFFFFFFF FF078069 FFFFFFFFFFFF

So it's pretty generic and writing should be possible, right? Can I write just key A for testing purposes on a tag?

@c64bob
Copy link
Author

c64bob commented Jul 12, 2017

Actually, just writing block 3 of sector 0 works. Maybe the problem is this: on the tag I'm trying to clone key B is not read and appears as "------------" in the dump. This probably causes the whole block not being written on the new tag. Do you have an idea why key B could not be dumped?

@ikarus23
Copy link
Owner

Oh yes indeed, that is correct. Blocks with unknown information will not be written. Mifare Classic only allows writing a full block and MCT can not do that unless the whole block is present in the dump.

@c64bob
Copy link
Author

c64bob commented Jul 12, 2017

This makes sense! So why is key B unknown - couldn't it be decrypted, or is it missing from the original tag (if that is even possible)?

@ikarus23
Copy link
Owner

MCT can not crack or decrypt keys. It just tries the keys that are in the key file. MCT comes with a bunch of well known keys. However, if your key is not in any of these files MCT can not find it for you.

Have a look at https://github.com/ikarus23/MifareClassicTool#getting-started

@c64bob
Copy link
Author

c64bob commented Jul 12, 2017

Thanks for the clarification

@c64bob c64bob closed this as completed Jul 12, 2017
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

2 participants