Thank you both for your helpful comments,
I used i2d_ASN1_OCTET_STRING now before including the data into the
certificate.
Is there any way to tell the OpenSSL x509 command line tool to display
these in a hex representation so they are human readable when we'd like
to inspect a certificate?
Hi,
Hex encoding surely ought to increase the size by a factor of exactly 2?
(Plus a few bytes for the tag and length.)
2 is correct without the colon but the OpenSSL function I use adds them.
Of course you are right, it would be possible with 2 :)
An extension has an OID, a criticality
decoder deco...@own-hero.net writes:
[...]
Ok, so what I am currently doing is something like
asndata = ASN1_OCTET_STRING_new();
ASN1_OCTET_STRING_set(asndata, myData, myLength);
and then I add asndata to an extension I create:
ex =
On Tue, Jun 08, 2010, Bruce Stephens wrote:
decoder deco...@own-hero.net writes:
[...]
Ok, so what I am currently doing is something like
asndata = ASN1_OCTET_STRING_new();
ASN1_OCTET_STRING_set(asndata, myData, myLength);
and then I add asndata to an
Hello,
I am currently developing an application that stores custom data in the
X509 client certificate. Some of this data is binary and I managed to
store it in a custom extension. Initially, I encoded this data using
i2s_ASN1_OCTET_STRING() to obtain a hex encoded version. When viewing
the
