Wireshark · Wireshark-dev: Re: [Wireshark-dev] XML Dissection in Wireshark

[Anders Broman <a.broman@xxxxxxxxx>]

upendra.allu@xxxxxxxxx skrev 2010-11-05 17:36:

Hi Anders,

 

Thanks for the reply, But what type of application you are talking about?

Here my main requirement is wireshark dissecting the XML files.

Yes, but what puts the data in the XML file? and why in that format?
/Anders

 

Regards,

Upendra

 

 

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx on behalf of Anders Broman
Sent: Fri 11/5/2010 4:12 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] XML Dissection in Wireshark

Hi,

Sorry, but the whole idea seems foolish to me. It would be much better to have the application outputting the xml data doing that in

either pcap format or some other binary data that's easier to parse than xml.

Just my 2 cents.

regards

Anders

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of upendra.allu@xxxxxxxxx
Sent: den 5 november 2010 15:58
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] XML Dissection in Wireshark

Hello,

 

I have some queries regarding XML data dissection in Wireshark.

Right now all the protocols in Wireshark can be dissected using "pcap" files.

 

Now I have a requirement to use XML data to dissect some of the(ranap, mtp3 etc..) Wireshark protocols. after doing some investigation, I found that in order to dissect xml data, separate dtd files need to be written for all the required plug-ins. Which are similar to the files in “dtds” directory in Wireshark source code. Once after that I have to integrate the dtd files into wireshark code so as to make them to dissect XML data. now the following are my queries.

 

1. How to write a DTD file for a protocol? (is there any standard format for that? if so, can any one please let me know?)

2. Once after writing the DTD file, how to integrate the file into wireshark base code? (is the normal source code compilation is enough? I don’t think it will be enough as it is separate file format in wireshark)

3. what additional changes are required for this in the wireshark?

4. Finally, is my above approach for dissecting XML data is correct?

If any one worked in above type of requirement please help me.

 

Regards,

Upendra

 

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

___________________________________________________________________________
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