Re: [TLS] Record layer corner cases
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TLS] Record layer corner cases



On 11/27/06, Peter Gutmann <pgut001 at cs.auckland.ac.nz> wrote:

I don't handle it at all, if my code sees OOB data in the middle of a TLS
stream it flags it as a network-level error (my security model is default-
deny).  I've never seen OOB data used and can't imagine why it'd ever be used
except as a potential attack vector targetting corner cases in TLS
implementations.

Evidently you've never used SIGURG, nor seen urgent data sent (that which causes TCP PSH headers to be generated in BSD-type stacks). I'd like to see the discussions from when TCP was designed as to what it was designed to be used for -- it would seem to be for metadata involving the connection. (This is akin to the TLS record protocol being used to request a rehandshake, since the TLS implementation consumes those records.)

I would think that such a concept could be useful in modification of
the trust parameters associated with the data stream (specifically,
notification of revocation or expiration of trust parameters would be
a good reason for it).

-Kyle H

_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.