I would prefer to move those protocols over to use packet-ber and be
autogenerated.
This would require code to do indefinite length in packet-ber
properly, somehting that is missing but not very hard to do, just time
consuming.
I can not do indefinite length right now for packet-ber so it might
be best in the short term to just modify the
asn.c code instead.
I did previously do a test acse dissector that was autogenerated by
asn2eth but incomplete. so it should definitely be possible to
convert them.
but there would be a lot of work to do so short term.
On 5/20/05, Yuriy Sidelnikov <YSidelnikov@xxxxxxxx> wrote:
> Hi,
> analyzing some new ftam trace files I found that the indefinite length in
> the ASN.1 is not so rare thing as I thought.
> So I would like to have correct ASN.1 API.
> The question is that neither obsolete asn1.c nor new packet-ber.c can handle
>
> with the indefinite length in asn.1 stream.
> So what is the better:
> 1.Add support for the indefinite length say "over" asn1.c.It is not very
> hard so we'll have working dissector pretty soon.Really I need only one
> thing more - to get correct length in case of the indefinite length.
> 2.Try to use new api in the packet-ftam/acse/pres keeping in mind that
> somebody will be so kind to add the support for the indefinite length. It's
>
> not very easy way to go.
>
> Regards,
> Yuriy Sidelnikov.
>
>
> .............................................................
>
> Программа создания веб-сайтов за два дня: http://web.sema.ru/
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>