Attached is a new version of packet-ber.c
which makes it able to handle indefinite length for
SEQUENCE, SEQUENCE OF and SET OF.
I have tested it with those very fev captures I do have that contains
indefinite length encodings and it seems to work but needs more
testing. In particular it needs testing to verify it hasnt caused any
regressions.
There are other contructions in ASN.1 as well in addition to SEQUENCE,
SEQUENCE OF, SET OF that can use indefinite length but I would need
example captures containing such to test with before i feel
comfortable to add it to packet-ber.c
Sid,
Do you have capture files containing FTAM protocol with or without
indefinite length encodings that I and Anders can test the pending
asn2eth autogenerated dissector with?
best regards
ronnie sahlberg
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
>
Attachment:
packet-ber.c.gz
Description: GNU Zip compressed data
