linux-kernel - Re: [RFC] NFC subsystem prototype

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Apr 2011 08:08:13 +0200
From:	Harald Welte <laforge@...monks.org>
To:	Lauro Ramos Venancio <lauro.venancio@...nbossa.org>
Cc:	linux-kernel@...r.kernel.org,
	Aloisio Almeida <aloisio.almeida@...nbossa.org>,
	Arnd Bergmann <arnd@...db.de>, Waldemar.Rymarkiewicz@...to.com
Subject: Re: [RFC] NFC subsystem prototype

Hi Lauro,

On Mon, Apr 11, 2011 at 08:31:11PM -0300, Lauro Ramos Venancio wrote:
 
> 2011/4/9 Harald Welte <laforge@...monks.org>:
>
> > 0) why not create a general RFID subsystem instead of locking it down to
> >   NFC?  NFC is sort-of a superset of ISO 14443, so it would make more
> >   sense to have a generic framework that can support not only Mifare + NFC
> >   but all types of ISO 14443 (A / B) as well as ISO 15693.  This would mean
> >   other applications like electronic ID cards and ICAO-compliant passports
> >   would fit into the picture - even though not being NFC
> 
> The prototype supports ISO 14443 (A/B), MIFARE, Felica and Jewel. It's
> straightforward to add ISO 15693 support. So I think it is possible to
> support these applications using the NFC subsystem.

Then I suggest renaming the system.  I think it is a bit confusing to call
something NFC if in fact it is a way more generic RFID system for most common
13.56MHz based systems.

In other words: NFC depends on ISO 14443, but ISO 14443 does not depend on NFC,
so it would be a bit unconventional or unintuitive to use a NFC subsystem to
talk with non-NFC ISO 14443 cards/transponders.

Also, I'm not quite clear what's the situation with regard to the NFC trademark,
i.e. if it wise to use the trademark.  There has been one previous case with
the 'firewire' situation, where firewire is the trademark and IEEE 1394 the name
of the technical specification - and the the Linux subsystem is alled
'ieee1394'...

> > 1) do you really think a kernel subsystem is the best idea for this?
> >   normally, the RFID/NFC ASIC is attached either to USB or serial lines,
> >   and there are no timing constraints against userspace drivers using libusb,
> >   like the existing libnfc or librfid.
> 
> The advantages appear when you consider the NFC peer-to-peer use case
> (LLCP). A socket interface for LLCP would fit better for implementing
> some features, such as OBEX over LLCP and IP over LLCP.

Ok, I fully agree for the case of OBEX and IP.  This did not occur to me when I
made my earlier comment.

Regards,
	Harald
-- 
- Harald Welte <laforge@...monks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/