Hi. Some time ago I was interested in the same thing (working with ACOS5
cards). Now our need is relaxed, but, time permitting, this is always
useful to us.
I was able to do also some secure operation directly on the card (I must
check my code), but I wasn't able to fully understand the structure
Gabriele Turchi wrote:
> I was able to do also some secure operation directly on the card (I must
> check my code), but I wasn't able to fully understand the structure of a
> card driver: there are so many cross references between different parts
> of the libraries...
I've started working on this
I ran into a problem recently when rebuilding opensc in an environment
where a version of the package was already installed (Fedora Core 6, gcc
4.1.1, with both opensc and opensc-devel installed).
The problem is that many of the opensc source files, but particularly
opensc.h, include files like th
On Monday 19 February 2007, Ian Young wrote:
> The problem is that many of the opensc source files, but particularly
> opensc.h, include files like this:
>
> #include
> #include
> #include
>
> Unfortunately, the <...> means to pick these files up from the globally
> installed
Ville Skyttä wrote:
> Wouldn't that be the rough equivalent of adding "." to $PATH and/or
> $LD_LIBRARY_PATH, ie. what stuff gets actually used would depend on in which
> dir a command pulling it in would be run? Doesn't sound too good to me when
> thinking about these same headers being insta
Dear folks,
I'm trying to figure out, why my D-Trust Micardo 2.0 signature card
fails when signing using the PKCS#11 driver. Apparently the PSO SIGN
command fails with SW1/SW2=6400.
How can I enable debugging, so that I can see the APDUs exchanged ? I'm
using SCB 0.7 and already have debug = 6 in
Ian Young wrote:
> From what you're saying, maybe the -I../../src/include option (either of
> them!) ought to be making the right thing happen, as that directory does
> include an opensc directory containing (soft links to) the appropriate
> files. Apparently not, though, and I don't know how to
Andreas Schwier wrote:
Dear folks,
I'm trying to figure out, why my D-Trust Micardo 2.0 signature card
fails when signing using the PKCS#11 driver. Apparently the PSO SIGN
command fails with SW1/SW2=6400.
How can I enable debugging, so that I can see the APDUs exchanged ? I'm
using SCB 0.7 and
SCB 0.7 is an oler version of opensc that needs to be compiled with
/DDEBUG to enable APDU logging. but it was compiled without.
new versions of opensc remove the /DDEBUG code and PADU logging
can be enabled with the debug level :8
Andreas
___
opensc-d
