<![CDATA[libnfc developers community]]> http://www.libnfc.org/community/ Thu, 09 Sep 2010 19:50:05 +0000 PunBB <![CDATA[pb with acces bits / how to restore factory default access bit ?]]> http://www.libnfc.org/community/topic/228/pb-with-acces-bits-how-to-restore-factory-default-access-bit/new/posts/ Hi,

I have some trouble with acces bits on my mifare classic 1k card, I have programmed the card with my dump of another card (all the keys are ok) but for sure I have made a mistake with trailer so I can't write or read the card now..... but authentication with key A|B is OK

It is possible to force write the trailer or restore it to factory default ? or the card is burn definitly ?

lu²

]]> Thu, 09 Sep 2010 19:50:05 +0000 http://www.libnfc.org/community/topic/228/pb-with-acces-bits-how-to-restore-factory-default-access-bit/new/posts/ <![CDATA[IO Data USB2-NFC - Working]]> http://www.libnfc.org/community/topic/224/io-data-usb2nfc-working/new/posts/ Hey guys I'm new to this smart card thing, but thanks to u guys
even I can get reading tags up and running in just a few days.
Thanks for all the hard work!

I'm using I-O Data USB2-NFC reader, PN531 chip inside from TOPPAN FORMS,
USB device (not a CCID) recognized under windows as TN31-NFC.

The driver came bundled but I had to build libnfc against libusb-win32 to get it working.
Getting it to work under windows is quite a tough time and I found
this thread by snapdev to be very useful.

I use CMake - Mingw32, not NMake though, so this is my list of changes:

  • included libusb-win23 header in /include/usb/usb.h

  • included usbstub.cpp by snapdev in /lib/usbstub.cpp

  • changes all include directive of <usb.h> to <usb/usb.h> (cosmetic ^^)

and this is my makefile

###############################################
# General settings
###############################################
VERSION = 1.3.4
SOURCE = ../src
NFC_LIB = $(SOURCE)/lib
NFC_INCLUDE = $(SOURCE)/include
NFC_BUSES = $(NFC_LIB)/buses
VPATH = $(SOURCE)/examples $(SOURCE)/examples/doc $(NFC_LIB) $(NFC_BUSES) $(NFC_LIB)/chips $(NFC_LIB)/drivers

###############################################
# Compiler settings
###############################################
CC = cl
LD = link
COMMONFLAGS = -O2 -GL -I "$(Include);$(INCLUDE)" -I "$(NFC_INCLUDE)" -I "$(NFC_BUSES)" -I "stdint" -D "WIN32" -MT -D "_CRT_SECURE_NO_WARNINGS" -D "HAVE_PCSC_LITE" -D "WIN32_DCOM" -D "_WIN32_WINNT=0x500" -D "_CRT_SECURE_NO_DEPRECATE" -D "NTDDI_VERSION=0x05000400" -D "DRIVER_PN531_USB_ENABLED" -D "DRIVER_PN533_USB_ENABLED" -D "DRIVER_ACR122_ENABLED" -D "DRIVER_ARYGON_ENABLED" -D "DRIVER_PN532_UART_ENABLED" -D "PACKAGE_VERSION=\"$(VERSION)\"" -D "_WINDLL" -EHsc -W3 -nologo -errorReport:prompt
CFLAGS = $(COMMONFLAGS) -TC
CXXFLAGS = $(COMMONFLAGS) -TP
LDFLAGS = -INCREMENTAL:NO -NOLOGO -MANIFEST:NO -OPT:REF -OPT:ICF -LTCG winscard.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib

###############################################
# Files
###############################################
OBJS = usbstub.obj pn53x.obj pn532_uart.obj acr122.obj arygon.obj bitutils.obj uart.obj nfc.obj pn53x_usb.obj pn531_usb.obj pn533_usb.obj
HEADERS = dev_acr122.h bitutils.h defines.h libnfc.h usb.h
LIBNFC = libnfc
EXES = nfc-anticol.exe nfc-list.exe nfc-emulate.exe nfc-relay.exe nfc-mfclassic.exe nfc-mfultralight.exe nfcip-initiator.exe nfcip-target.exe quick_start_example1.exe

all: $(LIBNFC) $(EXES)

usbstub.obj: usbstub.cpp
    $(CC) -c $(CXXFLAGS) $< 
pn53x.obj : pn53x.c
    $(CC) -c $(CFLAGS) $< 
pn532_uart.obj : pn532_uart.c
    $(CC) -c $(CFLAGS) $< 
acr122.obj : acr122.c
    $(CC) -c $(CFLAGS) $< 
arygon.obj : arygon.c
    $(CC) -c $(CFLAGS) $< 
bitutils.obj : bitutils.c
    $(CC) -c $(CFLAGS) $< 
uart.obj : uart.c
    $(CC) -c $(CFLAGS) $< 
nfc.obj : nfc.c
    $(CC) -c $(CFLAGS) $< 
pn53x_usb.obj : pn53x_usb.c
    $(CC) -c $(CFLAGS) $< 
pn531_usb.obj : pn531_usb.c
    $(CC) -c $(CFLAGS) $< 
pn533_usb.obj: pn533_usb.c
    $(CC) -c $(CFLAGS) $< 
    
libnfc:  $(OBJS)
    $(LD) $(LDFLAGS) -OUT:$(LIBNFC).dll -DLL -DEF:"libnfc.def" -SUBSYSTEM:WINDOWS $(OBJS)

%.exe : %.c $(LIBNFC) 
    $(CC) $(CFLAGS) -TC -I "$(NFC_LIB)" $< /link /OUT:$@ -SUBSYSTEM:CONSOLE $(LDFLAGS) $(LIBNFC).lib

clean: 
    del /Q $(OBJS) $(LIBNFC).dll $(LIBNFC).exp $(LIBNFC).lib *.obj $(EXES)

*I don't understand makefiles too much, how do u differ *.c from *.cpp ?

of course, how to install libusb-win32 is not covered here.

So perhaps we can update this device compatibility list to TESTED-OK?
once again, to all developers and contributors, thank you very much!

]]> Thu, 09 Sep 2010 13:48:11 +0000 http://www.libnfc.org/community/topic/224/io-data-usb2nfc-working/new/posts/ <![CDATA[MFCUK - MiFare Classic Universal toolKit]]> http://www.libnfc.org/community/topic/229/mfcuk-mifare-classic-universal-toolkit/new/posts/ Few months ago, Andrei Costin works on tk-libnfc-crapto1, a toolkit that allow to retrieve Mifare Classic keys without knowing them.

Renamed MFCUK for MiFare Classic Universal toolKit, this project based on libnfc provide a simply command line to recove whole keys of a Mifare Classic in few minutes.

http://code.google.com/p/mfcuk

Now, this project is looking for contributors to bring MFCUK works with libnfc 1.3.9, I already did some works be applying API changes to MFCUK but I can't get it works with the lastest libnfc. If somebody have some knowledge in Mifare Classic hacking and wants to improve this tool, please contact me or Andrei Costin to gain an SVN access to MFCUK project.

]]> Thu, 09 Sep 2010 06:04:20 +0000 http://www.libnfc.org/community/topic/229/mfcuk-mifare-classic-universal-toolkit/new/posts/ <![CDATA[General question / shopping guide ;)]]> http://www.libnfc.org/community/topic/226/general-question-shopping-guide/new/posts/ Hi,

I have a general question regarding libNFC and its hardware support. My plan is to build a simple wireless connection between two NFC devices without any error correction. Is this possible? Does it depend on the hardware? I want to buy two devices. Which hardware can you recommend? I guess there are some devices which are better supported than others, or?
Maybe, someone can share his experiences...

Regards,
Tim

]]> Thu, 09 Sep 2010 05:45:01 +0000 http://www.libnfc.org/community/topic/226/general-question-shopping-guide/new/posts/ <![CDATA[How to write NDEF data into Mifare Classic 1k/4k]]> http://www.libnfc.org/community/topic/227/how-to-write-ndef-data-into-mifare-classic-1k4k/new/posts/ Hi all,

I was trying to write the example NDEF data that is present at the below link in Mifare 1K tag.

But when I try to read with my Tag read application (Propritory), it is saying NDEF data not found.
Is there any procedure to write the NDEF data into Mifare1K?
If you have any example NDEF raw data, pls provide me.

Note: I started writing the NDEF data from the Block 1 of Sector 0 (as Block 0 of the sector 0 contains "Manufacturer data".
I am using ACR 122 tag reader/writer.

Thanks,
Nagendra

]]> Wed, 08 Sep 2010 13:08:57 +0000 http://www.libnfc.org/community/topic/227/how-to-write-ndef-data-into-mifare-classic-1k4k/new/posts/ <![CDATA[libfreefare-0.2.0 is out!]]> http://www.libnfc.org/community/topic/225/libfreefare020-is-out/new/posts/ The libfreefare team is pround to announce the release of libfreefare-0.2.0!

This new version introduce support for Mifare DESFire targets, and fix a few issues.  A complete list of supported targets is available on the project page [1], and the tarball is available in the download section [2].

Get it while it's hot!

References:

  1. http://code.google.com/p/nfc-tools/wiki/libfreefare

  2. http://code.google.com/p/nfc-tools/downloads/list

]]> Tue, 07 Sep 2010 18:26:52 +0000 http://www.libnfc.org/community/topic/225/libfreefare020-is-out/new/posts/ <![CDATA[lsnfc: simple command for POSIX systems]]> http://www.libnfc.org/community/topic/83/lsnfc-simple-command-for-posix-systems/new/posts/ POSIX systems users usually known commands like lspci, lsusb or lspcmcia; I'm happy to announce that lsnfc now exists.
It was written for debugging purpose but it is already usable.

Output examples:

$ lsnfc
device = ACR122U102 - PN532 v1.4 (0x07)
  ISO14443A: NXP MIFARE DESFire (UID=04453501db2480)
  ISO14443A: NXP MIFARE DESFire (UID=042e4201db2480)
  ISO14443A: NXP MIFARE DESFire (UID=04145109db2480)
  ISO14443A: NXP MIFARE DESFire (UID=04443401db2480)
  ISO14443A: NXP MIFARE DESFire (UID=04400b09db2480)
5 tag(s) have been found.
$ lsnfc
device = ACR122U102 - PN532 v1.4 (0x07)
  ISO14443A: NXP MIFARE Classic 1K (UID=fccd5dd3)
  ISO14443A: NXP MIFARE Classic 1K (UID=5c6c5ed3)
  ISO14443A: NXP MIFARE Classic 1K (UID=6c185fd3)
3 tag(s) have been found.
$ lsnfc
device = ACR122U102 - PN532 v1.4 (0x07)
  ISO14443A: NXP MIFARE Ultralight (UID=04652e91212580)
  ISO14443A: NXP MIFARE Ultralight (UID=04ce4591212580)
  ISO14443A: NXP MIFARE Ultralight (UID=047a3991212580)
3 tag(s) have been found.

lsnfc is a part from nfcutils package in nfc-tools project (http://code.google.com/p/nfc-tools/).
As a part of nfc-tools, nfcutils is under GPL license and contributions are welcome.

]]> Tue, 07 Sep 2010 16:32:14 +0000 http://www.libnfc.org/community/topic/83/lsnfc-simple-command-for-posix-systems/new/posts/ <![CDATA[libnfc 1.3.x releases]]> http://www.libnfc.org/community/topic/131/libnfc-13x-releases/new/posts/ Dear developers,

We are proud to announce the new version 1.3.0 of libnfc.

This release would not have been possible without the help of the following contributors:
- Adam Laurie
- Emanuele Bertoldi (Zuck)
- François Kooman (fkooman)
- Roger Brown (snapdev)
- Romain Tartière (romain)
- XXV
and others... ;-)

There are many fixes, improvments and changes:

Fixes:
 - build: Add workarounds for libusb when compiling using C99;
 - build: Attempt to fix rpath issue on linux platform (it is already deprecated in main distributions. i.e. http://wiki.debian.org/RpathIssue);
 - build: wrong paths in pkg-config file;
 - libnfc: Remove warnings when compiling;
 - libnfc: Various code fixes and cleanup;
 - bus uart: Added support for recv/send of larger data chunks (>default_os_buffer);
 - bus uart: Fix some some buffer synchronization problems under POSIX system;
 - bus uart: Add configure option: --disable-serial-autoprobe to disable autoprobing;
 - libnfc: Fix nfc_target_init doesn't correctly reset the parity during initalization;
 - libnfc: added support for WUPA and 7,10 byte UID in nfc_initiator_select_tag();
 - libnfc: Fix tag re-selection with UID length > 4 bytes (like DESFire or Ultralight);
 - nfc-mfclassic: Fix authenticated only with KEYA;

Improvments:
 - build: Build on FreeBSD;
 - build: Add alternative build system (CMake);
 - build: Add new files usefull for desktop GNU/Linux users: some rules for udev to allow non-root access to PN53x USB devices;
 - build: Update msinttypes up to revision 26. (used when compiling under Windows);
 - build: Add "make doc" directive: it will build API documentation using Doxygen. (--enable-doc flag is required at configure time);
 - libnfc: Add C++ compatibility;
 - libnfc: Add driver agnostic nfc_pick_device(), nfc_list_devices();
 - libnfc: It is now possible to specify a wanted device using new struct "nfc_device_desc_t";
 - libnfc: Add device name to device descriptions (nfc_device_desc_t) to select a given PCSC device;
 - libnfc: Finally removed all dirty globals, it 'should' be thread-safe now;
 - libnfc: Less confusing message for bitstreams display;
 - libnfc: chips level introduction with pn53x.h/c;
 - drivers: Add PN532 UART driver;
 - drivers pn533_usb and pn531_usb: Lets search continuing to find other USB readers if any in PN531 and PN533 USB drivers;
 - drivers pn533_usb and pn531_usb: Support for the generic vendorid/productid of the NXP chip;
 - drivers pn533_usb and pn531_usb: Consolidate duplicated code;
 - examples: Add MIFARE Ultratag tool;
 - examples: Add man page for nfc-mfultool;
 - examples: MIFARE examples (mftool and mfultool) have now a better help message;
 - examples: Add NFCIP (NDEP) as experimental feature;
 - examples: add quiet mode to improve timing of emulate, relay and anticol commands;
 - nfc-list: List all devices in nfc-list(1);
 - nfc-list: Simply turns off the RF field upon exit;
 - nfc-emulate: allow UID to be specified;
 - nfc-relay: Initialize initiator device explicitly;
 - nfc-relay: Capture ctrl-c for quitting cleanly the relay attack application;
 - nfc-relay: exit properly if emulator initialization failed;
 - nfc-mfclassic: Add default keys tries;

Changes:
 - API: Rename tag_info to nfc_target_info_t;
 - API: Rename init_modulation to nfc_modulation_t;
 - API: Rename dev_config_option to nfc_device_option_t;
 - API: Use NULL instead of INVALID_DEVICE_INFO to know if device is valid;
 - API: Rename chip_type to nfc_chip_t;
 - API: Rename dev_spec to nfc_device_spec_t;
 - API: Rename dev_info struct to nfc_device_t;
 - API: Variables have been renamed to match coding conventions;
 - API: Changed length parmeters from uint32_t to size_t;
 - Files: Remove defines.h public header;
 - Files: Prefix messages.h and types.h headers by "nfc-";
 - Files: Revamp libnfc source tree;
 - Files: Move examples into src/examples subdirectory;
 - Examples: Rename nfc-mftool to nfc-mfclassic;
 - Examples: Rename nfc-mfultool to nfc-mfultralight;

Archives are available for both POSIX compliant systems and Windows as the usual location
http://code.google.com/p/libnfc/downloads/list

Have fun !

]]> Tue, 07 Sep 2010 16:16:04 +0000 http://www.libnfc.org/community/topic/131/libnfc-13x-releases/new/posts/ <![CDATA[difficulty loging in to forum]]> http://www.libnfc.org/community/topic/223/difficulty-loging-in-to-forum/new/posts/ Hello,


For quite some time now I've been having problems logging into this forum.
The forum allways came back with errors about cookies that could not be set etc. ; very annoying.
Then, after a tip from Romuald, I found out that the forum does work, as long as you tick the ' remember me' button.
Maybe it's something other people might like to know.
It helps a bit when trying to post a question :-)


Regards,
Tom

]]> Mon, 30 Aug 2010 11:25:43 +0000 http://www.libnfc.org/community/topic/223/difficulty-loging-in-to-forum/new/posts/ <![CDATA[Bugs in svn for Arygon reader]]> http://www.libnfc.org/community/topic/222/bugs-in-svn-for-arygon-reader/new/posts/ Hi,

I'm working with the serial driver of arygon on the trunk, and have notice that you are modify quite a few thinks in the past days.

As a tester I will point out some stuff you should change:
- uart.c --> uart_xxx are no longer returning bool so in arygon.c you should change the transcieve to put it to <0 instead of !=0
- arygon.c --> the device name, in line 165 is not well copied. In the PCSC devices the name is adquired from the driver but in arygon serial it is never stored in pndd->acDevice. You should set as it was in previous versions to ARYGON_READER_NAME or similar
   ----> line not correct : strncpy(pnd->acName, pndd->acDevice, DEVICE_NAME_LENGTH - 1);
The issue is that in arygon_list_devices you copy it correctly as it is hardcoded ARYGON.

Hope that helps you out. Really good job, but the changes are making me driving mad. The issue is I cannot use the libfreefare with old versions of libnfc wink

Besides that I will in a few day point you something also for libfreefare.

See you

]]> Mon, 30 Aug 2010 07:30:38 +0000 http://www.libnfc.org/community/topic/222/bugs-in-svn-for-arygon-reader/new/posts/ <![CDATA[Cannot use libnfc on Win7 32Bit]]> http://www.libnfc.org/community/topic/221/cannot-use-libnfc-on-win7-32bit/new/posts/ Hello to everybody.
I did not have the time to follow the project but on holidays I tried and had some problems.
First of all I deleted svn folder and re downloaded all code from SVN.
Then I tried to follow readme-windows.txt with cmake-gui method but I get a strange error during linkin, something like "Error 0x02" ?!?!?!?!?
So I opened windows folder and typed simply nmake and I could compile with no errors....but...
if I try to run for example nfc-list.exe with a card in the reader, it crashes, and it crashes more or less with all the other examples.
The strange is that nfc-list for example says it's using 1.3.4 version.

So I opened my Ubuntu 10.04 virtual machine and re downloaded from svn everything, compiled, and it works well with both Touchatag and Snapper USB, nfc-list works perfectly and it says it's using 1.3.9 release (r566).

What can I try to use it in Windows 7 Pro ?
I also tried to use in Windows Console using "Run as Administrator" with no effect.

What do I missed to do ?

Can you provide 1.3.9 windows binaries ?

Thanks

Leo

]]> Tue, 24 Aug 2010 10:57:05 +0000 http://www.libnfc.org/community/topic/221/cannot-use-libnfc-on-win7-32bit/new/posts/ <![CDATA[Is Ehuoyan YHY632 compatible with libnfc?]]> http://www.libnfc.org/community/topic/220/is-ehuoyan-yhy632-compatible-with-libnfc/new/posts/ This is a Mifare Reader wich works via serial port. In it's board there is a MFRC500, a STC90C58RD+ and an RS232-TTL signal converter. Is there any chance for this RFID work with libnfc?

Sorry for bad english.

]]> Tue, 24 Aug 2010 06:38:49 +0000 http://www.libnfc.org/community/topic/220/is-ehuoyan-yhy632-compatible-with-libnfc/new/posts/ <![CDATA[Unknown SAK reply]]> http://www.libnfc.org/community/topic/196/unknown-sak-reply/new/posts/ I have a card which replies with the following
ATQA (SENS_RES): 00 04
UID (NFCID): 8E BB 32 40
SAK (SEL_RES):53 04 00 00

So it is a MIFARE CLASSIC tag but the SAK doesn't correspond to any reported here..
http://www.libnfc.org/documentation/har … s/iso14443

What one has to do in these cases?

]]> Thu, 19 Aug 2010 12:08:36 +0000 http://www.libnfc.org/community/topic/196/unknown-sak-reply/new/posts/ <![CDATA[Authentication against Nokia 6212's secure element]]> http://www.libnfc.org/community/topic/213/authentication-against-nokia-6212s-secure-element/new/posts/ I use a serial reader Feig CPR M02 and Nokia 6212 unlocked.
If i use gpshell, helloworld.cap to install, i get:
C:\work>GPShell.exe helloworld.txt
mode_211
enable_trace
establish_context
card_connect
* reader name FEIG ID CPR.M02.VP/AB-C 0
open_sc -security 3 -keyver 42 -mac_key 404142434445464748494A4B4C4D4E4F -enc_ke
y 404142434445464748494A4B4C4D4E4F -kek_key 404142434445464748494A4B4C4D4E4F
–> 00CA006600
80502A0008313BBBE336A0B41400
8482030010F26A412631967224AA134965F70D8C0B
80E400800C4F0AA00000006203010C010100
80E400800B4F09A00000006203010C0100
80E602001809A00000006203010C0100000AEF08C60201B0C80200640000
80E80000EFC48201A5010013DECAFFED010204000109A00000006203010C0102001F0013001F
000E00150036000C0067000A00130000006C00000000000002010004001502040107A00000006201
01000107A000000062000103000E010AA00000006203010C0101001406000C008003010001070100
00001F070067000210188C000118110100900B8700188B00027A02308F00033D8C00043B7A052319
8B00052D198B0006320329041F651B1A08AD0016041F8D00073B16041F41290419088B00083270E6
198B00093B19160408418B000A1903088B000B19AD000316048B000C7A08000A0000000000000000
000005003600
load_applet() returns 0x8010002F (Error comunication with smartcard.)

The authentication work (9000) but not the installation.

I try with jcManager:

Open terminal …
EstablishContext(): …
Wait for card in a certain reader …
Pick reader …
**********************
Selecting Card Manager
***********************
-> 00 A4 04 00 08 A0 00 00 00 03 00 00 00
80 50 00 00 08 1D 22 78 4F 0E D7 94 F8
84 82 03 00 10 E6 5C E7 00 CE FB EF 37 13 A1 05 B1 CF 64 79 FB
<- 69 82
Could not authenticate. Aborting.

why authentication is not working? keys just the same.

Thanks, good work.

]]> Thu, 19 Aug 2010 11:44:05 +0000 http://www.libnfc.org/community/topic/213/authentication-against-nokia-6212s-secure-element/new/posts/ <![CDATA[Mifare Emulation - Clarification?]]> http://www.libnfc.org/community/topic/208/mifare-emulation-clarification/new/posts/ Ok, it's said that mifare emulation can't be done with a usb NFC reader due to timeing issues, what that actually causes these timing issues?

Secondly, if thats the case, does anyone know if emulation could occur through a serial interfaced to an NFC chipset instead?

Also, a side question, does anyone know somewhere that sells PN53x chips in realtively low quanities? DigiKey seems to only sell them in the hundreds, so not really very helpful for this kind of thing.

Thanks to any and al replies smile

]]> Thu, 19 Aug 2010 11:37:20 +0000 http://www.libnfc.org/community/topic/208/mifare-emulation-clarification/new/posts/