I'm trying to compile libnfc 1.7 for windows 7 and I've hit a snag after solving a couple of other problems. After configuring everything in cmake 2.8.11 I want to do a mingw32-make which produces the following error. I checked the code and it definitely IS declared. So every error in there is false but it won't ignore them. What to do?

C:\dev\libnfc-build>cmake-gui .

C:\dev\libnfc-build>cmake-gui .

C:\dev\libnfc-build>mingw32-make
Scanning dependencies of target nfc
[  1%] Building C object libnfc/CMakeFiles/nfc.dir/nfc.c.obj
[  3%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-device.c.obj
[  5%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-emulation.c.obj
[  7%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-internal.c.obj
[  8%] Building C object libnfc/CMakeFiles/nfc.dir/conf.c.obj
[ 10%] Building C object libnfc/CMakeFiles/nfc.dir/iso14443-subr.c.obj
[ 12%] Building C object libnfc/CMakeFiles/nfc.dir/mirror-subr.c.obj
[ 14%] Building C object libnfc/CMakeFiles/nfc.dir/target-subr.c.obj
[ 15%] Building C object libnfc/CMakeFiles/nfc.dir/drivers/acr122_usb.c.obj
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c: In function 'acr122_usb_rec
eive':
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:3: error: 'off_t' undecl
ared (first use in this function)
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:3: note: each undeclared
 identifier is reported only once for each function it appears in
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:9: error: expected ';' b
efore 'offset'
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:630:20: error: 'offset' unde
clared (first use in this function)
libnfc\CMakeFiles\nfc.dir\build.make:249: recipe for target `libnfc/CMakeFiles/n
fc.dir/drivers/acr122_usb.c.obj' failed
mingw32-make[2]: *** [libnfc/CMakeFiles/nfc.dir/drivers/acr122_usb.c.obj] Error
1
CMakeFiles\Makefile2:79: recipe for target `libnfc/CMakeFiles/nfc.dir/all' faile
d
mingw32-make[1]: *** [libnfc/CMakeFiles/nfc.dir/all] Error 2
makefile:135: recipe for target `all' failed
mingw32-make: *** [all] Error 2

C:\dev\libnfc-build>

I changed some parameters in the TgInitAsTarget and now I´m working with a Netduino instead of an Arduino. Now I have good responses but I have some doubts............I configure the PN532 to work as a passive target in ISO/IEC 14443-4 PICC mode at 106 kbps. When I tap the phone to the shield I have the next data back:

E0 80 36 00 03 9F 3D 79 06 BE 62 AF 7C DD 00 00 00 32 46 66 6D 01 01 11 02 02 03 80 03 02 00 01 04 01 64 DA D2 6D 01 01

This data is some kind of LLCP PDU??? Analyzing it first seems to be an AGF PDU with a 36 byte PDU in it.........but the suposed inside PDU doesn´t have sense, so i don´t know what could be............

- Timeout: ACR122 does have troubles with timeouts, used through PC/SC or not (ie. acr122-pcsc or acr122-usb driver).
That's not related to PC/SC at all.

- Blocking functions: a PC/SC command can not be cancelled, which is a requirement for P2P / act as target.

So, the fact that ifdnfc (ifdhandler for nfc devices) does not have troubles is absolutely not related in any point to these ones.

ifdnfc is a tools to use libnfc's compatible devices as a PC/SC reader... that's not the same that ACR122 does have its own PC/SC.

I am asking because there is also the ifdhandler in beta that supposedly should make it possible to use libnfc compatible readers to the PC/SC stack, and I don't see the purpose of that if the timeout issue is a problem.

Regards,

Johan Henselmans

The new version worked (and I fixed the sudo nfc-list issue by copying the correct udev file), but for some reason the system doesn't automatically log me in until I click on the username I wish to log in with. This was on Ubuntu 12.04 with gdm, with 'auth sufficient pam_nfc.so' in /etc/pam.d/login and /etc/pam.d/gdm respectively.

Thank you,

Thank you,

Thank you,

My process is following.
-I connect ACR122 to the Windows PC by USB.
-I bump the android terminal to the ACR122.
-I execute TgInitAsTarget command of PN533 from the PC to ACR122.
I set DEP connection(0x40) in SEL_RES.
-Gi in ATR_REQ means LLCP connection in response of TgInitAsTarget.

Thank you,

pam_nfc was not up to date.

I tried to quick (and maybe dirty) update the code without testing it (I'm quite busy right now) but you could test it yourself and give some feedback here :

Use pam_nfc from svn,

svn co http://nfc-tools.googlecode.com/svn/trunk/pam_nfc
cd pam_nfc
autoreconf -vis
./configure
make clean all

Hope it helps.

Bye

I'm trying to get ACR122U working on Ubuntu 12.04. I've installed libnfc-1.7.0-rc7 (also tested with libnfc-1.7.0-rc6 ) and pam_nfc-0.1.4 . Both installs go through fine and my nfc-list shows the device and tag:

$ sudo nfc-list
nfc-list uses libnfc 1.7.0-rc6
NFC device: ACS / ACR122U PICC Interface opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04  
       UID (NFCID1): a6  14  34  fc  
      SAK (SEL_RES): 08  

I should note here that running the command without sudo returns this:

nfc-list uses libnfc 1.7.0-rc6
error    libnfc.driver.acr122_usb    Unable to claim USB interface (Operation not permitted)
nfc-list: ERROR: Unable to open NFC device: acr122_usb:003:003

I've tried adding the nfc to blacklist in /etc/modprobe.d/, unfortunately without success.

If I try adding user to the tag

sudo pam-nfc-add dejan

I get a segfault:

kernel: [ 2586.693391] pam-nfc-add[2640]: segfault at 0 ip 006e2848 sp bfbf6fa0 error 6 in libnfc.so.4.0.0[6df000+1b000]

Any suggestions? Is this procedure even correct for the acr122u? Thanks in advance for answers.

Best regards,

Dejan

I'm trying to make a fuzzer for NFC (and libnfc in particular) using an Android device (with Cyanogenmod to be able to emulate tags). As far as I know at the moment, Android is only capable of using NFC using APDU's.

The PCD I'm using is a tikitag with firmware ACR122U1.

I've managed to communicate between the PCD and the 'tag' (thus, Android device) in Java using the smartcardio library on my PC (PCD-side). What I'm trying now is doing the same but with libnfc in C or C++. The problem is I don't know how to send APDU's (or something similar so the NFCAdapter in Android will pick up the frame) with libnfc.

The anti-collision in C works just fine, but when trying to send an InDataExchange, it stops and waits forever for a reply.

REQA          | 26
ATQA          | 04  00
SEL (all)     | 93  20
UID, BCC      | 08  b8  c3  15  66
SEL (tag)     | 93  70  08  b8  c3  15  66  1f  0f
SAK           | 60  f8  32
RATS          | e0  50
ATS           | 05  78  33  88  00  59  b2

A normal APDU for PCD to tag would be something like this:

0xFF, 0x00, 0x00, 0x00, 0x04, 0xD4, 0x40, 0x01, 0xBA

In this example, the first 4 bytes are a pseudo-APDU to make sure the APDU is sent directly to the tag. The next byte is the length of the APDU itself. The 0xD4 0x40 0x01 is the InDataExchange command, telling all following bytes are data to be exchanged with the tag.

Any help is appreciated.