A VNC dissector file has been added to the
Ethereal svn archives; however it has not yet been included in a formal release,
the latest version being 0.10.10. More than likely it will be included in the
next release, assuming the author(s) and core Ethereal developers feel that it
is ready for inclusion. Until then, please be patient, or better yet, check
out the svn version and help contribute to its accuracy and usefulness! Hey,
no matter how good something is, there’s always room for improvement,
right? Personally, I think that the protocol itself, namely RFB (for Remote
Frame Buffer) is a more appropriate name than VNC. Perhaps it will be changed;
perhaps not. J Please refer to the attached RFB protocol description
document for why I feel the name change is relevant.
Regards,
Chris
P.S. I haven’t apologized recently
for the stupid disclaimer that my company automatically appends to all its employees’
outgoing e-mails, so I’m probably due for another one. Sorry! (No
really, I am sorry. I wish I could come up with a solution to prevent, avoid,
or otherwise circumvent this nonsense.)
-----Original Message-----
From:
ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of N.Allison
Sent: Wednesday,
March 30, 2005 9:37 PM
To: ethereal-dev@xxxxxxxxxxxx
Subject: [Ethereal-dev] VNC
Support?
Are you aware of any Ethereal
filters that have been made available for the VNC (Virtual Network Computing)
protocol?
If not, may I respectfully submit a
starting point for inclusion in your package?
This email may contain confidential and privileged material for the sole
use of the intended recipient(s). Any review, use, retention, distribution
or disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact the
sender by reply email and delete all copies of this message. Also, email is
susceptible to data corruption, interception, tampering, unauthorized
amendment and viruses. We only send and receive emails on the basis that we
are not liable for any such corruption, interception, tampering, amendment
or viruses or any consequence thereof.
Attachment:
rfbproto.pdf
Description: rfbproto.pdf