Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 3460] data decompression/processing

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 12 May 2009 17:50:04 -0700 (PDT)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3460





--- Comment #1 from Guy Harris <guy@xxxxxxxxxxxx>  2009-05-12 17:50:04 PDT ---
I'm not sure to what forms of "processing" you're referring, but there are
several places in Wireshark where packet data is decompressed or decrypted or
otherwise processed and put into a new tvbuff and dissected.

What would be an example of the sort of processing that couldn't be done with
Wireshark as it exists today?


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  • References:
    • [Wireshark-bugs] [Bug 3460] New: data decompression/processing
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 3460] New: data decompression/processing
  • Next by Date: [Wireshark-bugs] [Bug 3460] data decompression/processing
  • Previous by thread: [Wireshark-bugs] [Bug 3460] New: data decompression/processing
  • Next by thread: [Wireshark-bugs] [Bug 3460] data decompression/processing
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation