SSL and TCP

Hello all,

I was reading the paper "Analysis of the IPSec Key Exchange Standard"
by Radia Perlman and Charlie Kaufman.
http://sec.femto.org/wetice-2001/papers/radia-paper.pdf
In Section 2.2 they have written the following:

"There is a problem in operating above TCP. Since TCP will not be
participating in the cryptography, it will have no way of noticing if
malicious data is inserted into the packet stream. TCP will acknowledge
such data and send it up to SSL, which will discard it because the
integrity check will indicate the data is bogus, but there is no way
for SSL to tell TCP to accept the real data at this point. When the
real data arrives, it will look to TCP like duplicate data, since it
will have the same sequence numbers as the bogus data, so TCP will
discard it. So in theory, IPSec's approach of cryptographically
protecting each packet independently is a better approach. "


When TCP has already acknowledged the data which is malicious according
to SSL, how will a retransmission by SSL cause the remote TCP to use
the same sequence number and cause the first end point's TCP to discard
it?

Thanks and Regards,
Prashant
pvsnmp [ Mo, 25 September 2006 17:48 ] [ ID #1478332 ]

Re: SSL and TCP

http://groups.google.com/group/comp.protocols.tcp-ip/browse_ thread/thread/8c98fbe8688bd41e/7413aead257b8824#7413aead257b 8824
pvsnmp [ Di, 26 September 2006 06:01 ] [ ID #1479836 ]
Miscellaneous » comp.security.misc » SSL and TCP

Vorheriges Thema: DoS modelling tool (research papers)
Nächstes Thema: HPSBUX02155 SSRT061235 rev.1 HP-UX CIFS Server (Samba) Local Unauthorized Access, Elevated Privilege