kamal kumar a écrit :
> Hi all,
> I need clarification. Is P15 emulation provided only
> for using certificates/keys from the card.
>
> As i told you earlier, I am emulating p15 structures
> for my card and trying to support operations like
> loading of keypair and certificate to card.
>
> Is ther
Timothy J. Miller a écrit :
> There is no getting around the enrollment trust problem. Most
> sensible smartcard and PKI deployments handle this via an enrollment
> ceremony that involves a face-to-face component.
As for enrollment trust problem, IMHO, using the secure channel is good
alternative
Andreas Jellinghaus a écrit :
> https://www.opensc-project.org/files/openct/testing/
> https://www.opensc-project.org/files/openct/testing/openct-0.6.12-pre3.tar.gz
>
> https://www.opensc-project.org/files/opensc/testing/
> https://www.opensc-project.org/files/opensc/testing/opensc-0.11.3-pre2.tar.
Douglas E. Engert a écrit :
>
>
> Tarasov Viktor wrote:
>> Andreas Jellinghaus a écrit :
>>> It would be good to have opensc 0.11.2 soon, so I made another
>>> pre-release with current trunk available:
>>>
>>> http://www.opensc-project.org/file
Andreas Jellinghaus a écrit :
> It would be good to have opensc 0.11.2 soon, so I made another
> pre-release with current trunk available:
>
> http://www.opensc-project.org/files/opensc/testing/
> http://www.opensc-project.org/files/opensc/testing/opensc-0.11.2-pre4.tar.gz
>
> Please test this and
Andreas Jellinghaus a écrit :
> I like the idea of adding secure messagin!
>
> but in general: I think it would be nice to be able to
> encrypt all communication. think of contactless smart
> cards, I don't want data like the certificate go over
> the air unencrypted for privacy reasons.
Hello,
U
Andreas Jellinghaus a écrit :
> Hi Viktor,
>
> I like the idea of adding secure messagin!
>
> but in general: I think it would be nice to be able to
> encrypt all communication. think of contactless smart
> cards, I don't want data like the certificate go over
> the air unencrypted for privacy reas
Hello,
I would like to discuss an extension for the libopensc API, that
implements secure messaging.
In the attachment there is the patch to the common OpenSC part.
The full patch was tested with Oberthur card.
(Java card, secure messaging is conform to GlobalPlatform .)
The main headlines are:
Hello,
will it be more appropriate to change the SC_FUNC_RETURN (and similar)
define
from:
#define SC_FUNC_RETURN(ctx, level, r) { \
...
}
to:
#define SC_FUNC_RETURN(ctx, level, r) do { \
...
} while(0)
Kind wishes,
Viktor.
___
opensc-devel mailing
Hello,
When forgetting the named PIN, that has reference which is not equal to -1,
the corresponding named_pin[] entry is not set to NULL.
It concerns the PINs for which both 'named_pin[]' and '*secret_cache'
have an entry.
(./opensc-0.11.1/src/pkcs15init/keycache.c +334)
In my case it results i
Andreas Jellinghaus a écrit :
not 100% sure, never used it myself, these are only my best guesses.
Markus Schatzl wrote:
"Secure Messaging" obviously negotiates a secure channel between
the reader and the smartcard, so that the signals cannot be
wiretapped. What I ask myself is how this channel
Hello,
I'm trying to increase the performance of the Oberthur card support and
to keep it compatible with the card file system expected by Oberthur's
middleware.
It's not completely PKCS#15.
So, the emulator solution seems quite attractive.
But, AFAIS, the emulator's API do not supports the pk
12 matches
Mail list logo
