Re: Please review wip/openct wip/opensc and wip/opensc-signer

OBATA Akio wrote:
> In opensc/options.mk,
> * ${PREFIX} should be replaced with ${BUILDLINK_PREFIX.pcsc-lite}

Mkay.

> * I don't know the ext of "libpcsclite.so" is good for all platform
>   (dylib for Darwin?  sl for HP-UX?)

I have no idea.

> And just a fun...
> opensc/openct both have pcsc-lite option, and opensc optionally
> depend on openct. pcsc-lite is used on opensc/openct independently?

This is a little bit complicated. Opensc is a driver for smartcards, 
openct is a driver for smartcard readers and security/pcsc-lite is a 
middleware to access smartcard readers via SCard API. Pcsc-lite is used 
normally together with security/ccid driver for smartcard readers 
conforming to CCID and ICCD specifications.

For majority of users it's sufficient to use pcsc-lite and ccid with 
opensc. This combination doesn't cover all use cases though. For example 
for cmx(4) PCMCIA reader I use in most of cases, openct is needed. Openct 
can used either directly by opensc or it can be compiled with pcsc-lite 
support - ie. readers supported by opnect (I'm not sure whether all of 
them though) can be used via pcsc-lite (via special handler).

So I made defaults reasonable which should cover most of cases:

app --> opensc --> pcsc-lite --> ccid
                           \
                             --> openct

But if someone wants to rule out pcsc-lite for whatever reason, he/she has 
the way - to compile opensc to use openct directly:

app --> opensc --> openct


I hope this clarifies things a little bit ;).


-- 
Hasso Tepper

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H