Re: [Opensc-devel] State of session locking support

[Martin V. <mv...@gm...>]

Hello,


On Fri, Nov 27, 2015 at 5:08 PM, Frank Morgner <
mo...@in...> wrote:

> Am Freitag, dem 27. November, um 14:48 Uhr schrieb Martin Vogt:
> > I looked at the patch/source, but I cannot test.
> > The Problem is, my StarCos 3.2 card currently does not
> > work with the D-Trust starcos 3.4 driver.
>
> PRs are welcome ;-)
>

I will see ;-). The ATR/Pin encoding patches are easy, but the testsuite
is not working.



>
>
> > typedef void* sc_card_state_t;
> >
>
> As far as I can see, all operations to use a card's key in C_Sign, for
> example, is carried out automatically (except the login): select
> application, set security environment, ... What should be the content of
> some sc_card_state_t?
>

This depends on the card. I would say that for starcos 3.x its the
directory path
and the password, this should work.

Thus:

typedef struct sc_starcos_card_state_s {
  char* path;
  char* password;
  int pass_encoding;
} sc_startcos_card_state_t;


I don't have that much experience in OpenSC, this was only a guess
how it could be done.
And if some cards have different needs, like these "auth cookies",
it can be handles in the card driver.



>
> What are "auth cookies" and where are they stored/generated?
>

it was mentioned in this thread, but I never used it.

> On Fri, Nov 13, 2015 at 2:38 PM, Alon Bar-Lev <alo...@gm...>
wrote:
>This is why a card should support authentication cookie as I outlined
>and some do.
>You use credentials to establish authentication and accept a cookie as
>a response.


regards,

Martin