Wireshark-dev: Re: [Wireshark-dev] Bug 6112 - ANSI map/tcap ReturnError can't dissect

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Thu, 15 Jan 2015 10:01:49 +0000

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: den 14 januari 2015 22:06
To: Reutemann, Alan
Cc: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Bug 6112 - ANSI map/tcap ReturnError can't dissect


On Jan 14, 2015, at 4:57 AM, "Reutemann, Alan" <areutemann@xxxxxxxx> wrote:

> I've recently encountered this bug where all ANSI ReturnError messages are flagged with malformed packet errors.  Has there been any movement towards a solution?  Do you know yet if this is an ASN1 level bug or perhaps something in the BER sequence dissector?

I have added some more info in https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6112 

I don't know the answer to either of those questions, so I'm CCing wireshark-dev.  It's generally not a good idea to ask individual members of the Wireshark developer team questions unless you know that they're working on the particular part of Wireshark about which you're asking.

> I'd be willing to test out any code fix if you have one available, pending or proposed, etc.  I've built the 1.12.2 tshark tool to help decode ANSI tcap/map messages and will keep it handy if you think a solution is available and I may be able to help in this capacity.
>  
> Thanks for your service to Wireshark and the community that uses it,
>  
> Alan Reutemann
> Transaction Network Services Software Development
> 
> 
> This e-mail message is for the sole use of the intended 
> recipient(s)and may contain confidential and privileged information of Transaction Network Services.
> Any unauthorised review, use, disclosure or distribution is 
> prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
> 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe