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-dev: Re: [Wireshark-dev] New dissector: exec (rexec) protocol

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


From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Mon, 3 Jul 2006 16:46:48 -0700

On Mon, Jul 03, 2006 at 10:54:00PM +0000, ronnie sahlberg wrote:

> I dont know how popular this protocol is today but since most of the 
> payload for this protocol would be ascii text it would be nice if the 
> decode of the payload were displayed line by line in the decode tree.

Thanks for your changes - I will review them and follow them in the 
future :)

I thought about decoding the ascii payload.. but programs running with 
exec don't always have ascii only.  The old application used at my work 
uses exec to drive a GUI on the client so it's all unreadable.  What do 
you think about doing a check to see if it is printable characters, and 
if so display it?


Steve


  • References:
    • [Wireshark-dev] Fwd: New dissector: exec (rexec) protocol
      • From: Stephen Fisher
    • Re: [Wireshark-dev] New dissector: exec (rexec) protocol
      • From: ronnie sahlberg
  • Prev by Date: Re: [Wireshark-dev] Next release (plus SVN and roadmap changes)
  • Next by Date: Re: [Wireshark-dev] Next release (plus SVN and roadmap changes)
  • Previous by thread: Re: [Wireshark-dev] New dissector: exec (rexec) protocol
  • Next by thread: [Wireshark-dev] patch to ISUP: add ANSI CRM, follow MTP3 standard preference
  • Index(es):
    • Date
    • Thread

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