nfc-mfclassic's output should be more clear about libnfc HOT 13 CLOSED

Mistake: that was since r136 that nfc-mftool try to read MIFARE Classic using
defaults key.

. => OK
x => wrong
(writing (OK) data to file : ...)

Do you have any suggestions to make this more readable ?:)

Yes Roel: like previously said: "If crosses are failures, we shouldn't have a 
"Done,
all bytes dumped to file!" message." isn't it ?

Agreed, let's get rid of the stupid message ;)

NOTE: This patch is not tested!

how it works this patch?

At first sight, this patch contains one error: switching from signed to unsigned
integer deny to be below under 0...so please don't use this patch if you don't 
know
how to fix it.

Well, there is another typo error: "print_success_of_failure" instead of
"print_success_or_failure".

For the un/signed problem, simply don't change the "iBlock" variable. But why 
we need
a signed counter?

This is a better version.

Zuck> For the un/signed problem, simply don't change the "iBlock" variable. But 
why
we need a signed counter?

If you check the for-loop:
> for (iBlock=uiBlocks; iBlock>=0; iBlock--)
You can see that for-loop will loop until iBlock < 0. And iBlock can't be 
negative if
it's unsigned.

BTW, thanks for patch. I will try to commit them in trunk on Monday 23th.

Romuald, this is clear, but that is the only signed counter in "classic" and
"ultralight" tools. Why we can't simply switch to an unsigned one and change the
guard condition?

Please, correct the typo error when you merge it to the trunk ;)

Patch have been applied in r212. Thanks you Zuck.