none
Can you help me identify this format? RRS feed

  • Question

  • Hello. I have this data that has been sniffed from a communication between a desktop client and a webservice hosted in an IIS server. I've been asked to parse it for debugging purposes but I don't have much more info from the developers. Do anyone recognize this .NET webservice input/output format?

    It looks like encoded XML to me. I've been doing some research and I think this may be related to MS-PCCRTP. I've been trying to decode in C# with BinaryMessageEncoding and XmlDictionaryReader with no success so far.

    I know it's a broad question, but ask me if you have any idea and need more info. Thank you very much.

    I can't place the link or image yet but you can download a sample file at:

    https://drive.google.com/open?id=0B4vxM3oIkhZaMDRkaEE3VmZRUms

    And a hex dump screenshot at:

    https://drive.google.com/open?id=0B4vxM3oIkhZaUWJtaUtnNjFMT1k



    • Edited by geqq Friday, March 24, 2017 3:22 AM
    Friday, March 24, 2017 3:12 AM

All replies

  • >> I have this data that has been sniffed from a communication between a desktop client and a webservice hosted in an IIS server.

    Do you mean you want to read information from test.dat? How did you get this file? As far as I know, it is not the input/output format for web service.

    As my researching, a file with the DAT file extension is usually a generic data file that stores information specific to the application, no specific program is responsible for creating or using every type of DAT file.

    I suggest you refer the link below for more information.

    # What Is a DAT File?

    https://www.lifewire.com/what-is-a-dat-file-2620550

    Disclaimer: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 24, 2017 4:40 AM
  • Hello.

    It was sniffed with SmartSniff. It's a tcp/ip stream, it just sets the .dat extension when you export the stream. test.dat is a sample.

    If it doesn't look like any standard MS format, then I guess the application should have a custom protocol.

    Thank you.



    • Edited by geqq Friday, March 24, 2017 4:56 AM
    Friday, March 24, 2017 4:54 AM
  • It is difficult to identity the format. WCF includes three types of encoding for SOAP messages: Text, Binary and MTOM. There are different properties for different Encoders. And we are not sure whether the message will use compression.

    #Choosing a Message Encoder

    https://msdn.microsoft.com/en-us/library/aa751889(v=vs.110).aspx

    For debugging, I would suggest you debug at client side.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 27, 2017 2:19 AM