linux-kernel - Re: Driver for a SmartCard interface on a SoC

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 12 May 2010 09:38:34 +0200
From:	Juergen Beisert <jbe@...gutronix.de>
To:	linux-kernel@...r.kernel.org
Cc:	Alan Cox <alan@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Jiri Slaby <jslaby@...e.cz>
Subject: Re: Driver for a SmartCard interface on a SoC

Hi Alan,

Alan Cox wrote:
> > > I'd say drivers/char if its a generic char device, but if its MX25
> > > specific code entirely then drivers/platform or arch/.../platform.
> >
> > This driver covers a SmartCard core built into this kind of CPU. Its
> > not like an interrupt controller which is specific to the CPU. Its a
> > component like the USB and LCD controller, also built into this CPU.
> > Maybe other CPUs will follow that are also using this SmartCard core
> > (I don't know, only the manufacture knows).
>
> The question is really about the interface as seen from userspace - is
> that generic or could it be generic so you could write other card
> drivers for different hardware to the same user space interface ?

Yes, the interface can be generic. As the main feature of these cards is the 
communication itself, there are only a few additional requirements to make it 
work. But these additional requirements are shared by all SmartCards. Where 
would be the best place/mail list to discuss this API?

> > > The other question is one of API - it's going to best if the API
> > > isn't MX25 specific but could reasonably be expected to work with
> > > other future devices. A fake tty interface is probably overkill for
> > > that but it would be good to get general review of any API.
> >
> > "faky tty"?
>
> Some systems have before now implemented onchip smart card interfaces
> with drivers that pretend to be a serial port talking a serial link to
> the smartcard.

Do you mean to emulate an external serial device in the kernel driver?
To make it understand the same data sequences these kind of external device 
understand? Would be possible, but its more complex than to run the 
communication via read()/write() and a few additional IOCTLs for the special 
SmartCard handling.

Regards,
Juergen
--
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/