[openssl-users] ASN1 & Recursive Structures definition

[Richard Levitte]

Ah, sorry then, I may have been wrong.  The forward declaration that's
actually needed seems to be this (one for each applicable type):

    DECLARE_ASN1_ITEM(TEST)

(I'm digging through the ASN.1 stuff myself, slowly learning)

Cheers,
Richard

In message <0089b413-278e-34b1-32b3-2e71b48e5540 at openca.org> on Sun, 3 Dec 2017 11:37:56 -0700, "Dr. Pala" <madwolf at openca.org> said:

madwolf> Hi Richard, all,
madwolf> 
madwolf> I tried to do the forward declaration also for the TEST_SIGNATURE together with the TEST one, but
madwolf> that did not really work :( It is still complaining about the use of 'sizeof' on an incomplete type. In
madwolf> particular, the two errors are:
madwolf> 
madwolf>  src/ocspv2/****: error: use of undeclared identifier 'TEST_it'
madwolf>  ASN1_EXP_SEQUENCE_OF_OPT(TEST_TBS, otherTests, TEST, 5),
madwolf>  ^
madwolf> 
madwolf>  and
madwolf> 
madwolf>  src/ocspv2/****: error: invalid application of 'sizeof' to an incomplete type 'const
madwolf>  ASN1_TEMPLATE []'
madwolf>  } ASN1_SEQUENCE_END(TEST_TBS)
madwolf>  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
madwolf> 
madwolf> I guess I need to checkout the macros a bit more.. :D
madwolf> 
madwolf> Question: does anybody know if there is any other structure already implemented in OpenSSL that
madwolf> resembles the one I am trying to do here? I tried to look for something similar, but no success.. :D
madwolf> 
madwolf> If there is no easy answer, I guess I will have to either change the envisioned approach (maybe
madwolf> introducing an intermediate data structure of some kind..?) or use the ASN1_ANY approach.
madwolf> 
madwolf> Cheers,
madwolf> Max
madwolf> 
madwolf> On 12/2/17 4:54 AM, Richard Levitte wrote:
madwolf> 
madwolf>  In message <d1eeba62-f25f-c984-dc77-94a150cf73c1 at openca.org> on Fri, 1 Dec 2017 20:22:09 -0700,
madwolf>  "Dr. Pala" <madwolf at openca.org> said:
madwolf> 
madwolf> madwolf> Hi Richard,
madwolf> madwolf>
madwolf> madwolf> thanks :D That worked. I have a new challenge for you now. Here's what
madwolf> madwolf> I am trying to do:
madwolf> madwolf>
madwolf> madwolf> ASN1_SEQUENCE(TEST);
madwolf> madwolf> ASN1_SEQUENCE(TBS_TEST) = {
madwolf> madwolf>     ASN1_SIMPLE(TBS_TEST, version, ASN1_INTEGER),
madwolf> madwolf>     ASN1_EXP_SEQUENCE_OF_OPT(TBS_TEST, otherTests, TEST, 0)
madwolf> madwolf> } ASN1_SEQUENCE_END(TEST)
madwolf> madwolf>
madwolf> madwolf> IMPLEMENT_ASN1_FUNCTIONS(TBS_TEST) [**]
madwolf> madwolf>
madwolf> madwolf> ASN1_SEQUENCE(TEST) = {
madwolf> madwolf>     ASN1_SIMPLE(TEST, tbsTest, ASN1_INTEGER),
madwolf> madwolf>     ASN1_EXP_OPT(TEST, optionalSignature, TEST_SIGNATURE, 0)
madwolf> madwolf> } ASN1_SEQUENCE_END(TEST)
madwolf> madwolf>
madwolf> madwolf> IMPLEMENT_ASN1_FUNCTIONS(TEST) [**]
madwolf> madwolf>
madwolf> madwolf> In this case, the difference is that TBS_TEST has, inside the
madwolf> madwolf> otherTests that are of type TEST. The TEST is built out of a tbsTest
madwolf> madwolf> and an optionalSignature - but it is defined after TBS_TEST.
madwolf> madwolf>
madwolf> madwolf> What to do in this case ?
madwolf> 
madwolf> It seems to me that you need to do some kind of forward declaration of
madwolf> TEST_SIGNATURE as well, before the construction of TEST.  (also, to be
madwolf> picky, you need to make sure that ASN1_SEQUENCE(TBS_TEST) is ended
madwolf> with ASN1_SEQUENCE_END(TBS_TEST), not ASN1_SEQUENCE_END(TEST))
madwolf> 
madwolf> Cheers,
madwolf> Richard
madwolf>