Hello,
Frank Morgner wrote:
What are the limitations in OpenSC?
>>> 1. There is no kind of abstraction in the current SM code. At the
>>> moment every card driver implements its own version of secure
>>> messaging.
SM is not implemented by card driver, but the separate SM pr
Hi!
On Tuesday, October 12 at 10:33AM, Viktor TARASOV wrote:
> >>> 1. There is no kind of abstraction in the current SM code. At the
> >>> moment every card driver implements its own version of secure
> >>> messaging.
>
> SM is not implemented by card driver, but the separate SM procedures.
> T
Frank Morgner wrote:
> Hi!
>
> On Tuesday, October 12 at 10:33AM, Viktor TARASOV wrote:
>
> 1. There is no kind of abstraction in the current SM code. At the
> moment every card driver implements its own version of secure
> messaging.
>
>> SM is not implemented by ca
As outlined below, in a note from 10/6, changes were committed (r4805)
today, with slight modifications.
o sc_pkcs15_pubkey_from_cert was moved from pkcs15-pubkey.c to pkcs15-cert.c,
and now calls parse_x509_cert. It no longer depends on OpenSSL, I can
now easily work with more then RSA
