Projects to release
- libfreefare for libnfc 1.7.0
- libnfc 1.7.1
- libnfc 1.8.0? with libusbx 1.0
- libfreefare in Debian?
Projects to fix
- MFCUK: it seems it does not work at all... (only 2 bytes are OK in keys)
- libfreefare to be fixed regarding coverity reports
- extend coverity scans of libnfc & libfreefare to flag reader/card data as tainted
Projects to revive
- nfcutils ? (revive or merge in libnfc's nfc-list ?)
- Process issues !!! (https://code.google.com/p/libndef/issues/list)
- Release a new version with bug fixes
- Switch to git
- libnfc on R-Pi (with tutorial here)
- Nfc-cryptorf: where is the code repo?? there is just an old zip completely desync with current API on that page
Who need it ? Why should we reuse it ? Does it really need to be in libnfc ? --Romuald It's like mfoc, useful for some security testing, it shouldn't be in libnfc but could be added to nfc-tools svn
- Libnfc:nfc-relay update info & now there is also nfc-relay-picc to present
- Libnfc:nfc-emulate update info & present nfc-emulate-forum-tag2, nfc-emulate-forum-tag4, nfc-emulate-tag, nfc-emulate-uid
- forum -> collect info & archive discussions
- pages with hacking/install/news/readme/readme-windows
- Migrate wikipages from https://code.google.com/p/libnfc/w/list
- Sandbox / pages people want to create without rights
- PN53x capabilities as target ISO14443-4 yes software -> yellow partly?
Maybe we should also implement a function to test if device is compiliant in libnfc...
Should we really update it since libnfc.org do not exists anymore ? --Romuald Those are not wiki pages, those are the generated API pages. We can migrate them on nfc-tools.org if you prefer but at least maintain them, no? They're currently linked from Libnfc:API --Phil
- m-extr nfc-tools?
What is that ? --Romuald Hmm good question, leave it till I remember ;-) --Phil
- NFC sybsystem incompatibility & future
- libnfc developers group https://groups.google.com/forum/?fromgroups=#!forum/libnfc-devel
- Topics not yet screened
- NDEF, SNEP, Android etc
At first, a recall of important point: to send a content from/to Android (or other NFC-Forum compliant), the content (URL, vCard, Text, etc.) should be encoded in a NDEF¹ format. During the communication between 2 devices, they poll for NFCIP connexion. Once connected, the software layer is ensured by LLCP². LLCP is a specification that offers a service-based protocol that could be compared to the network socket-system basics : one service (ie. in network FTP, in NFC SNEP³ or NPP⁴) affected to one port (ie. in network 21 for FTP, in NFC 4 for SNEP). When LLCP communication is established, one of the devices will ask for SNEP service on Android 4.x.x and for NPP service on Android 2.3.x on the target. With this short explanation, you should oriented to understand basics, for further details you should read according specifications.
 NDEF: NFC Data Exchange Format  LLCP: Logical Link Control Protocol  SNEP: Simple NDEF Exchange Protocol  NPP: Android NDEF Push Protocol http://static.googleusercontent.com/external_content/untrusted_dlcp/source.android.com/en//compatibility/ndef-push-protocol.pdf