Ethereal-dev: Re: [Ethereal-dev] Re: Patch for indefinite length for packet-ber.c
Hi,
as I know it is not possible only difference to SEQUENCE is that the order of items can
be arbitrary (for BER).
Tom
Anders Broman (AL/EAB) wrote:
Hi,
Just glancing at the patch so I might be wrong ... but can't an occurance in a SET occure multiple times?
Brg
Anders
-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx]On Behalf Of Tomas Kukosa
Sent: den 26 augusti 2005 15:21
To: graeme@xxxxxxxxxxx; Ethereal development
Cc: tim@xxxxxxxxxxxxxxx
Subject: Re: [Ethereal-dev] Re: Patch for indefinite length for packet-ber.c
Hi,
I have never used tvb_composite_...() but is in it enough to use tvb_composite_...()
instead of all reassemble mechanism?
Tom
Graeme Lunt wrote:
Tim, Anders,
Can you grab the latest svn, as I have been making a number of fixes
over the last few weeks as different traces have been made
available(thanks). The first bug is dealt with in a different way now
but the second is valid.
I have attached my latest version with your fix done, can you
check that it still works with your nested indefinite length traces.
I've gotten the latest version out of svn and everything looks good with my
traces (my second fix had already been incorporated).
I attach a patch to packet-ber.c to fix:
a) dissect_ber_octet_string() to reassemble constructed OCTET STRINGs
b) dissect_ber_set() to report missing fields and handle untagged CHOICEs
c) dissect_ber_choice() to handle untagged CHOICEs (within the CHOICE)
Graeme
------------------------------------------------------------------------
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
--
_________________________________________________
ANF DATA ANF DATA spol. s r. o.
a SIEMENS Company MediaHall, Bidláky 20
639 00 Brno
Czech Republic
Tomáš Kukosa Tel.: +420 - 533 337 227
PSE ECT PSS 2 Fax : +420 - 533 337 252
Room: 2.64 mailto:tomas.kukosa@xxxxxxxxxxx
_________________________________________________