Hello,
Thank you for your response. I'll try to clear up a
few things: I don't want to rewrite the ASN1 parser,
but I want to be able to decode each value separately.
I already have classes that, using the openssl parser,
decode the basic types (integer, enum, octet string,
bit string etc). So, I
On Thu, Feb 02, 2006, Enis Arif wrote:
> Please, if someone can give me an answer to my
> problem, because I have to take a decision to use
> openssl for the project or not. Is it feasible to
> modify the d2i_ASN1_SET/ASN1_item_d2i/ASN1_item_ex_d2i
> behavior or is it an easier way to do it?
>
I
Please, if someone can give me an answer to my
problem, because I have to take a decision to use
openssl for the project or not. Is it feasible to
modify the d2i_ASN1_SET/ASN1_item_d2i/ASN1_item_ex_d2i
behavior or is it an easier way to do it?
__
Do
Hello,
I have a problem with sequence unpacking. Given the
following code
ASN1_TYPE *at = NULL;
STACK_OF(ASN1_TYPE) *st = NULL;
st = ASN1_seq_unpack_ASN1_TYPE(asn1->get_data(),
asn1->get_len(), d2i_ASN1_TYPE, ASN1_TYPE_free);
if I call
at = sk_ASN1_TYPE_value (st, 0)
I get the sequence members
