On Wed, 2010-10-06 at 23:12 +0300, Martin Paljak wrote:
> Hello,
>
> On Oct 6, 2010, at 7:10 PM, Douglas E. Engert wrote:
> > PROPOSAL:
> >
> > I would like to do the following to cleanup some of the duplication:
> >
> > Replace sc_pkcs15_pubkey_from_cert with non OpenSSL code, that would
> > us
On Wed, 2010-10-06 at 13:08 -0500, Douglas E. Engert wrote:
>
> On 10/6/2010 12:11 PM, Andre Zepezauer wrote:
> > Hello Douglas,
> >
> >> One of the operations I need for the PIV card is to get the public
> >> key from the certificate, as pubkey needs to be emulated for thes cards.
> >
> > Please
Hello,
On Oct 6, 2010, at 7:10 PM, Douglas E. Engert wrote:
> PROPOSAL:
>
> I would like to do the following to cleanup some of the duplication:
>
> Replace sc_pkcs15_pubkey_from_cert with non OpenSSL code, that would
> use the sc_asn1_decode_algorithm_id, and other code from parse_x509_cert
> t
On 10/6/2010 12:11 PM, Andre Zepezauer wrote:
> Hello Douglas,
>
>> One of the operations I need for the PIV card is to get the public
>> key from the certificate, as pubkey needs to be emulated for thes cards.
>
> Please could you explain, why it is required to extract the public key
> from the
Hello Douglas,
> One of the operations I need for the PIV card is to get the public
> key from the certificate, as pubkey needs to be emulated for thes cards.
Please could you explain, why it is required to extract the public key
from the certificate within OpenSC. I know that other emulators do
One of the operations I need for the PIV card is to get the public
key from the certificate, as pubkey needs to be emulated for thes cards.
OpenSC has more then one way to do this, but only RSA keys are currently
supported.
./pkcs15-pubkey.c has sc_pkcs15_pubkey_from_cert, but this relies on
OpenS
