On 03.05.2007, at 1:36, Martin Preuss wrote: > I don't think that reader manufacturers care that much about Linux > (some do, > but the majority doesn't). Meanwhile we have to deal with the > situation as it > is.
Agreed. But also - if there is clear indication from the community - what do you want and how do you want it - it is easier to convince manufacturers to work on the support. Having a mixed picture is not that appealing. > [...] > On the lowest layer I need at least: > - support for different driver types (especially IFD and CTAPI, > since there > still are drivers for both interfaces) > - commands: > - look for a card, wait for insertion if necessary > - lock/unlock a card > - send commands > - release card > - information: Manufacturer of the reader, driver/firmware version > if possible > etc. This is needed for abstraction of differences in APDU's on > different > readers. > - access to both processor *and* memory cards > > In addition I'd like to have (and therefore implemented it in > Libchipcard): > - secure access to readers at remote hosts (not as remote as via > internet but > within an intranet) This has been done with openct as well as pcsclite. A unified solution for this problem would also be appreciated (Especially if it would be cross-platform) > - the master-slave model described in the document Micha linked to > in his > mail), this is needed for thin-client support provided for Gnumed Quickly going through the doc - the only reason for this is the remote access reason, right ? > [...] >> Libchipcard works on Windows (partially). This means it SHOULD work >> on linux/mac via pcsclite as well >> (given my assumption that most ctapi drivers are implemented on top >> of pcsc is correct). > [...] > It *does* work over PC/SC, but that interface doesn't let me use > CTAPI drivers > so it excludes those readers for which there only are CTAPI drivers > (which > could of course be circumvented by adding an IFD-CTAPI wrapper). On windows - do you use CTAPI drivers and are there any readers that only have ctapi and no pcsc drivers? > Also, currently there is no standard way how to use memory cards on > every > PC/SC implementation: pcsclite allows me to connect such cards by > specifying > the protocol "raw" but that doesn't work on Windows and it also > doesn't work > with some proprietary (binary-only) readers. > > And last, but certainly not least, is the issue with the > definitions of DWORD > etc which prevents mixing of 32- and 64 bit clients with one pcscd > (or have > this meanwhile been solved? And what about the byteorder stuff? Is > that > solved?) Needs investigation (comments from Ludovic?) Three issues I can harvest: 1. CTAPI bridge for pcsc (Possible to use code from openct?) 2. remote connections (should work with all combinations and hopefully be cross platform as well) 3. memory cards (No real solution ?) Time to sleep. -- Martin Paljak _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
