My understanding is that to convert the form of ecc key from compressed to
uncompressed and from uncompressed to compressed require the knowledge of
the ECC private key.
Is my understanding correct?
You might want to have a look at sections 2.3.3 and 2.3.4 in
I had this problem, too. A workaround that does the trick for me is to
- encode the key and any certificate you'd like to export to the .p12 as PEM
- Paste the PEM key and all the PEM certificates into one single file
(let's assume all.pem)
- then issue the following command:
openssl pkcs12
OK, I guess this is the only way to go then. Thanks for the help!
Regards,
Martin
2010/11/9 David Schwartz dav...@webmaster.com:
On 11/6/2010 7:44 AM, Martin Boßlet wrote:
I just tested, whether the BER-encoding is preserved if I do not alter
any of the contents. Unfortunately, it seems
Thanks for this, I'll have a look at the streaming features then!
Best regards,
Martin
2010/11/6 Dr. Stephen Henson st...@openssl.org:
On Fri, Nov 05, 2010, Martin Bolet wrote:
I'm sorry, I was not precise here. Actually I think (have to verify it
again though) the encoding is preserved if I
String in
constructed form with inifinite length, which was DER-encoded in
primitive form using definite length in the output.
Is there a way how I can circumvent the reencoding?
Best regards,
Martin
(BTW: I'm using 0.9.8o, maybe it's different in 1.0.0?)
2010/11/6 Martin Boßlet martin.boss
It's actually even worse. It's not just specific parts of the
SignedData such as the encapsulated content info that are BER-encoded,
it seems as if any set or sequence is encoded using constructed and
infinite length. Thanks for the information, I'll try using the CMS
functions and see how far I
Hello all,
I face the following problem: I have to parse PKCS#7 SignedData structures,
some of which use BER encoding for the EncapContentInfo content, the
Certificate and CRL sets and also the unsigned attributes set inside the
signer info. The CAdES standard (ETSI TS 101 733 V1.8.1) requires
OK, great, one thing less to worry about!
But I still face a problem with the explicit [0] tagged content of
EncapContentInfo. In this particular case it has an indefinite length
tag. When I i2d it again , the element is DER-encoded using definite
length and content. Can I force the use of the
force to use indefinite length
instead of the DER definite length bytes?
Regards,
Martin
2010/11/5 Martin Boßlet martin.boss...@googlemail.com:
OK, great, one thing less to worry about!
But I still face a problem with the explicit [0] tagged content of
EncapContentInfo. In this particular case
