Wireshark mailing list archives

Re: asn2wrs conformance TYPE_ATTR problem


From: Anders Broman <anders.broman () ericsson com>
Date: Tue, 3 May 2011 09:29:17 +0200

 

-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Risto Paasila
Sent: den 3 maj 2011 08:39
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] asn2wrs conformance TYPE_ATTR problem

OCTET STRING means a sequence of octets opaque to the protocol nothing 
to do with STRING as in text.
an implementation of the protocol can chose to put text in an OCTET STRING.
For example UserID := OCTET STRING can contain 0xfffff or "MyID".
You can use #.TYPE_ATTR to change hf definition but formally you 
should probably put code in the conformance file to check if the OCTET 
STRING contains printable characters and then output it as a string. 
Unless theres is something in the protocol description saying that the 
OCTET STRING should contain text there is no guarantee that it will.
Regards
Andes


Thanks. You're right of course that I should do checking.

What I was getting at was why doesn't it output the FT_STRING type into the HF array?

Regards
Risto
Did I miss something? a arbitrary long field of binary data can not be FT_STRING.
/Anders
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: