On Thu, 24 Feb 2011 22:41:50 +0100 Michael wrote: MT> > Sure. I've now got 1.0.0d from the openssl tarball on the server side, MT> > and openssl-1.0.0b-1.fc13.i686 on the client side. I fired up wireshark MT> > on my local machine (the client) to see what was going on. MT> > MT> > I've seen three scenarios so far: MT> > MT> > > Client Hello Seq# 0 MT> > > Client Hello Seq# 1 MT> > > Client Hello Seq# 2 MT> > MT> > > Client Hello Seq# 0 MT> > > Client Hello Seq# 1 MT> > < Server Hello Seq# 6 MT> > > Client Hello Seq# 2 MT> > < Server Hello Seq# 12 MT> > MT> > > Client Hello Seq# 0 MT> > > Client Hello Seq# 1 MT> > < Server Hello Seq# 0 MT> > > Client Hello Seq# 2 MT> > < Server Hello Seq# 6 MT> MT> how do you get the client to send these sequence numbers? The same for the server?
I'm not doing anything. I'm just reporting the numbers I'm seeing via wireshark. The server is long running, but the client is run fresh from the command line eash time, so a sequence number of 0 makes sense. MT> I don't understand how you get things into these states... MT> Maybe you can send us (privately) a Wireshark trace sure. -- Robert -- Senior Software Engineer SPARTA (dba Cobham Analytic Soloutions)
signature.asc
Description: PGP signature
