Ulf Lamping wrote:
Andrew Hood wrote:
Reading
gzipped pcap files does work.
That's the next I will look for - how to do this in a clean.way for all
compiler variants.
The simplest solution would probably be to not download zlib123 but
instead to download the source zlib-1.2.3 and
On 1/4/07, Martin Mathieson [EMAIL PROTECTED] wrote:
On 1/3/07, Guy Harris [EMAIL PROTECTED] wrote:
Martin Mathieson wrote:
For the more general problem, I see 2 possible solutions:
(1) have both signed and values in the union, and use the appropriate
signed or unsigned parts of the
Andrew Hood wrote:
The simplest solution would probably be to not download zlib123 but
instead to download the source zlib-1.2.3 and compile it. That way the
same MSVCR* gets used throughout.
I've checked it in a change that MSVC 6 runs like before, while every
other version downloads the
On Sun, Jan 07, 2007 at 10:28:46PM -0800, Gerald Combs wrote:
Don't lower-case our SSID and passphrase, otherwise we'll create an
incorrect PSK hash.
The code still makes another mistake: The SSID is not a string - it's a
binary object which may even contain 0x00 in the middle. The
Hi,
I think thats a good idea. But perhaps we should wait a day or two to
see if we get any complaints on
The new ANSI MAP dissector and the plans to move the files.
Lets say that if no one oposes we'll move the files on Wednesday.
BR
Anders
-Original Message-
From: [EMAIL PROTECTED]
Hello,
I just wanted to know if someone is already at work with a plugin for the
802.15.4 protocol in wireshark ?
I didn´t find any folder in the plugin section and wanted to start on the
plugin.
Jan
___
Wireshark-dev mailing list
Joerg Mayer wrote:
On Sun, Jan 07, 2007 at 10:28:46PM -0800, Gerald Combs wrote:
Don't lower-case our SSID and passphrase, otherwise we'll create an
incorrect PSK hash.
The code still makes another mistake: The SSID is not a string - it's a
binary object which may even contain 0x00 in the
Davide Schiera wrote:
What about wpa-phx:MyPassword:SSID WITH\x00INSIDE?
And for the : - \x3A or \:?
That would work too. Along with C-style encoding there's RFC 3986-style
percent encoding, e.g. SSID WITH%00INSIDE and My%3aPassword. Does
anyone strongly prefer one over the other?
Laurent Rabret wrote:
Hi Andrew,
Maybe your linker errors stems from bad compiler options. Initially I
recommended to remove some default libs and to force msvcrxx thanks to
/DEFAULTLIB and /NODEFAULTLIB options in LOCAL_LDFLAGS (in
the config.nmake file). Actually, it was probably a bad
Hi,
I've updated the patch for ptvcursor taking into account the ideas of Guy.
Features supported by ptvcursor :
- multiple levels (256 max.), allocation per 8 levels.
- Two new functions creating an item in the tree and pushing a subtree at the
same time. These two functions accept an
On Mon, Jan 08, 2007 at 09:42:38PM -, Mike Davies wrote:
There was a change in Corrigendum 1 (03/2004) to H.248.1 which allows
an empty {} to be omitted from the Signal Descriptor. Currently (SVN
20346) this causes Wireshark to report [Packet size limited during
capture] as shown in
After spending (wasting) several hours debugging my SNMPv3 USM
authentication code I found out that our md5 implementation is
broken!
It returns just plain wrong digests!
12345 should yield 827ccb0eea8a706c4c34a16891f84e7b
but instead it yields cad0f574e6b876f5248314742bb09b7c
I'll see if I can
OK I will commit changes tomorrow if no complain is received.
Meantime I will look again at SSL/TLS desegmentation which makes me
headache.
Mailcode: C0gmHhFp
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anders Broman
(AL/EAB)
Sent: Monday, January
On Jan 8, 2007, at 10:30 PM, [EMAIL PROTECTED] wrote:
Could anyone please explain how the above values produced such
display ( version : 4 , header length : 24 , etc. ) in the wireshark
gui.
Step 1: order a copy of
TCP/IP Illustrated, Volume 1
and read chapters 1, 2, and 3.
14 matches
Mail list logo
