On 03/28/11 17:21, Alon Levy wrote:
>> > Where does this odd LONG type come from? I think Windows uses LONG so
>> > having your own type would conflict with that, and of course we don't
>> > really want Windows types directly in QEMU either, so I am curious?
>> >
> This comes from pcsclite (which
On Mon, Mar 28, 2011 at 03:27:49PM +0200, Jes Sorensen wrote:
> On 03/23/11 14:19, Alon Levy wrote:
> > diff --git a/libcacard/passthru.c b/libcacard/passthru.c
> > new file mode 100644
> > index 000..d78e2db
> > --- /dev/null
> > +++ b/libcacard/passthru.c
> > @@ -0,0 +1,609 @@
> > +/*
> > + *
On Mon, Mar 28, 2011 at 03:27:49PM +0200, Jes Sorensen wrote:
> On 03/23/11 14:19, Alon Levy wrote:
> > diff --git a/libcacard/passthru.c b/libcacard/passthru.c
> > new file mode 100644
> > index 000..d78e2db
> > --- /dev/null
> > +++ b/libcacard/passthru.c
> > @@ -0,0 +1,609 @@
> > +/*
> > + *
On 03/23/11 14:19, Alon Levy wrote:
> diff --git a/libcacard/passthru.c b/libcacard/passthru.c
> new file mode 100644
> index 000..d78e2db
> --- /dev/null
> +++ b/libcacard/passthru.c
> @@ -0,0 +1,609 @@
> +/*
> + * implement the applets for the CAC card.
> + *
> + * This work is licensed under
From: Robert Relyea
In this mode libcacard doesn't emulate a card, but just passes apdu's
straight to the underlying card.
Not to be confused with ccid-card-passthru, which doesn't use libcacard
at all. So with this functionality in libcacard you can talk directly
to the host accessible card, fo
