#define the SSL 3.x message types in decimal, as they're decimal in the
spec.
#if 0-out some tables that would be used if we dissected some messages.
Move some of the unimplemented SSL 3.x message cases to be in numerical
order by message type (and appearance in the TLS 1.0 spec).
svn path=/trunk/; revision=8050
dftest.c:
Remove #if-0-ed includes
packet-ieee80211.c, packet-wtls.c, packet-afp.c, packet-wsp.c,
packet-wtp.c, ethereal_gen.py:
Remove redundant include varargs (already in snprintf.h,
and required only for snprintf.h)
Remove unused include of snprintf.h from files not using
"snprintf()".
svn path=/trunk/; revision=5889
the tvbuff we're handed.
Handle record headers split across segment boundaries.
Don't set the column until we know we don't need to desegment.
svn path=/trunk/; revision=5035
set the columns, for use with EAP payloads inside RADIUS packets.
From Adam Sulmicki: dissect SSL-encoded stuff inside EAP.
svn path=/trunk/; revision=4806
arguments to "proto_tree_add_text()", and to "proto_tree_add_XXX()" calls
that add FT_NONE or FT_PROTO items to the protocol tree, with -1.
Replace some calls to "tvb_length()" or "tvb_length_remaining()" with
calls to "tvb_reported_length()" and "tvb_reported_length_remaining()",
as those give the actual length of the data in the packet, not just the
data that happened to be captured.
svn path=/trunk/; revision=4605
"epan/..." pathnames, so as to avoid collisions with header files in any
of the directories in which we look (e.g., "proto.h", as some other
package has its own "proto.h" file which it installs in the top-level
include directory).
Don't add "-I" flags to search "epan", as that's no longer necessary
(and we want includes of "epan" headers to fail if the "epan/" is left
out, so that we don't re-introduce includes lacking "epan/").
svn path=/trunk/; revision=4586
being done; otherwise, it contains random data. As such, don't use it
as a way for the SSL2 and SSL3 record dissectors to indicate to the
top-level SSL dissector that the last record is continued in a
subsequent TCP segment - pass a pointer to a flag and have the record
dissectors set that flag if they record that we need to do
desegmentation.
svn path=/trunk/; revision=4556
structure to the "packet_info" structure; only stuff that's permanently
stored with each frame should be in the "frame_data" structure, and the
"column_info" structure is not guaranteed to hold the column values for
that frame at all times - it was only in the "frame_data" structure so
that it could be passed to dissectors, and, as all dissectors are now
passed a pointer to a "packet_info" structure, it could just as well be
put in the "packet_info" structure.
That saves memory, by shrinking the "frame_data" structure (there's one
of those per frame), and also lets us clean up the code a bit.
svn path=/trunk/; revision=4370
take a dissector handle as an argument, rather than a pointer to a
dissector function and a protocol ID. Associate dissector handles with
dissector table entries.
svn path=/trunk/; revision=4308
of protocol-id-plus-datum pairs, so that multiple protocols can attach
information to the same conversation.
Dissectors that attach information to a conversation should not assume
that if they find a conversation it has one of its data attached to it;
the conversation might've been created by another dissector.
svn path=/trunk/; revision=3901
FT_NONE, not FT_STRING, as they have no value assigned to them.
Don't use "hf_ssl_handshake_certificate" both for the collection of all
certificates and for individual certificates, add a new
"hf_ssl_handshake_certificates" FT_NONE field for the collection of all
certificates, as is done for other collections.
Properly pluralize the "N specs" in the item for the collection of
cipher specs.
Properly label the second "ssl.record" as "SSLv2 record data", not
"Length of SSLv2 record data".
Fix a typo in the field name of the field for the length of the
collection of certificates.
svn path=/trunk/; revision=3725
Opaque fields should be FT_BYTES, not FT_STRING; FT_STRING is for text
strings.
Don't supply a null value when putting an FT_BYTES field into the tree;
supply a pointer to the actual bytes.
For items with subtrees, use "proto_tree_add_text()" if the actual value
of all the stuff under the subtree, treated as a big array of bytes,
isn't interesting (e.g., if the individual items are put into the
protocol tree). Also, make the items with subtrees refer to the same
data as all the items under them.
svn path=/trunk/; revision=3724
Olivier Biot