[Call for Testers] Announcing Mifare DESFire support in libfreefare!

Great work Romain!

It is nice to see that related projects seem to get more and more body every day
Maybe I can help you in the future with some new cards (like the Plus and the Ultralight C).

Cheers,

  Roel

Hi bigjay.

This error is related to endianness conversion functions: FreeBSD provides a set of functions, OpenBSD another one, and old GNU libc does not provide such macros.  Since there is no POSIX solution that would work everywhere, there is some glue in <freefare_internal.h> so I updated it.

If you update at revision 463 it should be okay.
http://code.google.com/p/nfc-tools/source/detail?r=463

Please note that I changed something I think was wrong regarding endianness on 32bit values in that glue. These functions are used in Mifare Classic value management functions, so if you use them, I utterly recommand checking it works using the regression test suite.  I have no spare machine ATM to test if it is okay unfortunately, so feedback would be really appreciated.

Thanks!
Romain

Wow, that was fast, man!!!

Thanks a lot. All compiles well - no errors :-D

It's really late here, so i will continue testing tomorrow/today.

Thanks again for the fast action!

Hey!

Yep, it looks like it is the problem: I only have a 4K card and I have not added a test such as the one in the Mifare Classic MAD tests to avoid manipulations of the card beyond it's capacity: the first test fails because the card is OOM (it tries to create a record file with 22 repords of 100 bytes each → 2200 > 2048) and the card is left with a master key the second test does not know so it fails too when authenticateing on an assumed blank card.

We can either reduce the numbre of records we store or ensure the card is large enougth to run the test suite.

Thanks for the feedback!

Hello,

Yep, run autoreconf in verbose mode:

autoreconf -vis

Not exactly: you have more information about autoreconf run and I didn't except more from that command...

Could you report your version of autoreconf, autoconf, autoheader, automake and libtoolize ?
Which is your platform ?

configure.ac:8: required file `../ltmain.sh' not found
autoreconf: automake failed with exit status: 1
guepardo libfreefare-desfire #

The dot-dot-slash before ltmain.sh sounds strange... How did you install libtool ?

Could you try with a fresh fetch of libfreefare-desfire ?

Hi *dudux.

Check that the ltmain.sh file does not already exists with wrong permission or is a dead symlink.  If unsure, extract another copy of the repository.

While unlikely, your libtool install may be broken.  The ltmain.sh script is installed in ${prefix}/share/libtool/config/ on my system, I guess it is basically the same for you.  Ensure you can find the script and try to purge and install again the package.

Hi

The code source in libfreefare's trunk is expected to build aganist the libnfc trunk.  As of r452 of libnfc, the API has been enhanced [1] and so it's the new API that the libfreefare uses.

Checkout and build libnfc's trunk [2] and it should be okay ;-)

We are planning to release a new libnfc version in a few weeks, we would then tag and release a new libfreefare version, allowing you to use official releases instead of checking out the projects' trunk.  Stay tuned!

Regards,
Romain

References:
  1. http://code.google.com/p/libnfc/source/detail?r=452
  2. http://code.google.com/p/libnfc/source/checkout

Hi

Looks like the binary can't find the library.  If you are running the program from the source code directory, (./example/nfc-list) it should definitively work since it is just a shell script that setup the LD_LIBRARY_PATH correctly (./libnfc/.libs/) before running the actual program (./example/.libs/nfc-list).  This is supposed to work regardless of any installation of the libnfc in any prefix.

If you are running an installed binary, you can check using ldd(1) the location of the libraries the dynamic libraries linker will use when running the program:

romain% ldd `which nfc-list`
/usr/local/bin/nfc-list:
    libnfc.so.0 => /usr/local/lib/libnfc.so.0 (0x800748000)
    libpcsclite.so.1 => /usr/local/lib/libpcsclite.so.1 (0x800953000)
    libusb.so.2 => /usr/lib/libusb.so.2 (0x800a5e000)
    libc.so.7 => /lib/libc.so.7 (0x800b6e000)
    libthr.so.3 => /lib/libthr.so.3 (0x800daf000)

It will also tell you what libraries it can't find.  Common causes are prefix problems, for example the library is installed in the /usr/local/lib directory while the system looks for the library in /lib and /usr/lib only on GNU/Linux.  You can try to remove the libnfc installed files, run ./configure using a sane prefix (--prefix=/usr) build and install the library again.

\o/ cool!

Well, there are no real-world application I am aware of (yet), but you can find quick'n'dirty examples in the libfreefare's "examples" directory, a more complete use of all the API in the test/test_mifare_desfire.c file (100% coverage actualy), and an overview of the API is available through the man pages.

Feel free to ask questions / send patches / suggest enhancements if something is not clear, so that the next official libfreefare release, introducing Mifare DESFire targets support, be even more awesome !:-)

Thanks!