> Maybe you can kluge something up, but at the time I learned the
> TCP/IP stuff (which was admittedly some years ago) not all TCP
> implementations even IMPLEMENTED out of band data, so we were
> taught not to assume that it would be available.
If you need to proxy through a different connectio
I (Charles B Cranston) wrote:
> Michael Sierchio wrote:
It cannot be emphasized more clearly: TCP is a byte stream protocol.
This is quite true.
... There is NO WAY in TCP to indicate in
an out-of-band way that there is a 'record break'.
This is not quite true. You can certainly send OOB data
v
Charles B Cranston wrote:
It cannot be emphasized more clearly: TCP is a byte stream protocol.
This is quite true.
... There is NO WAY in TCP to indicate in
an out-of-band way that there is a 'record break'.
This is not quite true. You can certainly send OOB data
via TCP. Urgent data are read
It cannot be emphasized more clearly: TCP is a byte stream protocol.
It sends a stream of bytes. There is NO WAY in TCP to indicate in
an out-of-band way that there is a 'record break'. You MUST either
dedicate a byte value to "end of record" or have a more complicated
scheme of delimiting your r
Dustin C. Locke wrote:
As I understand it, SSL is a layer 4 (transport layer) protocol used in
conjunction with TCP (located slightly above TCP on the OSI heirarchy,
depending on whom you ask).
Slightly above? TCP is not part of OSI, it's TCP/IP.
I also realize that SSL "objects" introduce thei
On Wed, 2003-06-11 at 00:20, David Schwartz wrote:
> > Thanks for the reply. I've read Netscape's SSL 3.0 draft twice...most of
> > the information is simply data type specification in Baukus Naur Form
> > with no reference to the construction of the packet itself.
>
> Since SSL is layered o
> Thanks for the reply. I've read Netscape's SSL 3.0 draft twice...most of
> the information is simply data type specification in Baukus Naur Form
> with no reference to the construction of the packet itself.
Since SSL is layered on top of a byte-stream protocol, there won't be any
specif
> Does anybody know where I can find a specific diagram/chart showing the
> number of bits, data content, and data type of all of the individual
> fields (header and body both) of an ssl packet? They're readily
> available for many other protocols (IP, TCP, NTP, etc.), but I am unable
> to find o
Dustin C. Locke wrote:
Thanks for the reply. I've read Netscape's SSL 3.0 draft twice...most of
the information is simply data type specification in Baukus Naur Form
with no reference to the construction of the packet itself.
It's not a packet protocol -- SSL sits atop TCP. Perhaps this is
the s
iagram.
Steven
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dustin C. Locke
Sent: Wednesday, 11 June 2003 11:39 AM
To: [EMAIL PROTECTED]
Subject: RE: SSL protocol packet format
Thanks for the reply. I've read Netscape's SSL 3.0 draft twice...most of
the i
Eric Rescorla's book, "SSL and TLS", has what you need. Anyone doing
SSL coding should probably have it on the shelf anyway, IMHO.
Also, you might want to check out ssldump, which can decrypt SSL
traffic given the appropriate keying materials.
Paul Allen
Dustin C. Locke wrote:
Does anybody know w
11 matches
Mail list logo
