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]

Message-ID: <20100513103340.10e4e0e3@linux.intel.com>
Date:	Thu, 13 May 2010 10:33:40 +0100
From:	Alan Cox <alan@...ux.intel.com>
To:	Juergen Beisert <jbe@...gutronix.de>
Cc:	linux-kernel@...r.kernel.org, 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

> 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?

Probably linux-kernel for the kernel view. I don't really know much
about smartcard user space to know if there is another list that might
also be useful.

If you don't get any feedback on an API you suggest I'd then just go
and implement and submit it.

> 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.

Agreed - and I don't think the extra complexity is worth it.
--
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/