Hello,
On Feb 14, 2011, at 12:47 AM, NdK wrote:
> On 13/02/2011 21:18, Martin Paljak wrote:
>>> $ pkcs15-init -S startssl.p12 -f PKCS12 -i 45 -a 2 -l "StartSSL auth"
>>> Using reader with a card: Gemalto GemPC Twin 00 00
>>> error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
>> Is this
On 13/02/2011 21:18, Martin Paljak wrote:
>> $ pkcs15-init -S startssl.p12 -f PKCS12 -i 45 -a 2 -l "StartSSL auth"
>> Using reader with a card: Gemalto GemPC Twin 00 00
>> error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
> Is this error normal? Does it happen with OpenSSL command lin
On 13/02/2011 14:38, Andreas Jellinghaus wrote:
> yes, smart cards are quite old technology, files can't grow on demand :(
I knew that.
> sorry, I know ono way to calculate such file sizes. all you can do is try and
> error.
Yup. Hard to predict correct size, since certs can be of different size.
Hello,
On Feb 13, 2011, at 2:59 PM, NdK wrote:
>
> $ pkcs15-init -S startssl.p12 -f PKCS12 -i 45 -a 2 -l "StartSSL auth"
> Using reader with a card: Gemalto GemPC Twin 00 00
> error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
Is this error normal? Does it happen with OpenSSL command l
I haveno clue about myeid cards.
but in general you need to edit the profile to set the size of the
*DF files ("directory" files, i.e. files with the list and attributes
of all certs / keys / whatever). If some fileis too small, all you can do
is erase the whole card and create a new pkcs#15 struct
On 13/02/2011 11:07, Tomas Gustavsson wrote:
> Did you try to specify the -i parameter when importing certificates?
> pkcs15-init --store-certificate cert.pem -v -i 45
> where i is the key_id?
>
> I didn't try with multiple certs actually, but that's how I imported
> certificates assigning them to
Did you try to specify the -i parameter when importing certificates?
pkcs15-init --store-certificate cert.pem -v -i 45
where i is the key_id?
I didn't try with multiple certs actually, but that's how I imported
certificates assigning them to a key. See
http://blog.ejbca.org/2010/03/using-pure-o
