El jue, 03-02-2011 a las 16:28 +0200, Martin Paljak escribió:
Hello,
On Jan 26, 2011, at 10:09 AM, Ludovic Rousseau wrote:
I just found the page SmartCardPKI [1] on the seek-for-android
project. The goal is to build OpenSC for Android. They provide a patch
[2] but I do not remember reading
http://www.nist.gov/nstic
http://www.whitehouse.gov/the-press-office/2011/04/15/administration-releases-strategy-protect-online-consumers-and-support-in
Why could NSTIC be called a smart card standard?
Well, because a flexible scheme for strong authentication requires that
you can distribute
Le 23/04/2011 23:59, NdK a écrit :
Hello all.
Just noticed that there's a constant defined for maximum number of ACLs,
but the raw value is used in the code. This should fix it at least in
pkcs15-lib.c :
$ diff -u pkcs15-lib.c.ori pkcs15-lib.c
--- pkcs15-lib.c.ori2010-12-22
On 24/04/2011 13:17, Viktor TARASOV wrote:
The using of SC_PKCS15INIT_MAX_OPTIONS is not appropriate in this context.
SC_PKCS15INIT_MAX_OPTIONS is the number of profile options that can be defined
as an argument for the pkcs15init operations .
So I can use up to 16 +'option' ? :)
If you
On 24/04/2011 14:18, Viktor TARASOV wrote:
It seems the root of the problem lies in the profile: changing
CRYPTO=$PIN to CRYPTO=NONE works around it, but it's surely sub-optimal.
What I wanted to say: shouldn't --insecure replace $PIN with NONE ?
For what I've understood, -a N makes $PIN in
