Hi Martin,
Viktor TARASOV wrote:
Martin Paljak wrote:
On Feb 3, 2010, at 18:41 , Viktor TARASOV wrote:
Maybe pin cache should be attached not to 'pkcs15_card', but to the
PIN 'pkcs15_object' ?
In object info there are path, reference, flags, ...
Why not. If objects get destroyed and don
Hi Martin,
Martin Paljak wrote:
On Feb 3, 2010, at 18:41 , Viktor TARASOV wrote:
Maybe pin cache should be attached not to 'pkcs15_card', but to the PIN
'pkcs15_object' ?
In object info there are path, reference, flags, ...
Why not. If objects get destroyed and don't leak it would pr
On Feb 3, 2010, at 18:41 , Viktor TARASOV wrote:
> Maybe pin cache should be attached not to 'pkcs15_card', but to the PIN
> 'pkcs15_object' ?
> In object info there are path, reference, flags, ...
Why not. If objects get destroyed and don't leak it would probably be as good.
--
Martin Paljak
h
Hi Martin,
imho, in sc_pkcs15_pincache_entry it would be useful to include path and
pin_reference.
The first one is useful for the 'local' PINs, the second is useful when
looking for
the PIN cache that corresponds to some ACL byte.
Maybe pin cache should be attached not to 'pkcs15_card', but to
