Bodo Moeller wrote:
> > ... I have the feeling that much of the kludginess of
> > the OpenSSL code is there to handle the fact that input arrives not
> > as whole SSL Record Layer units, but in dribs and drabs, and lots of
> > effort is expended in tracking where you are, and being able to resume
> > at that point in the middle of a record on the next call.
> > In a purely event-driven model, where the events corresponded to full
> > SSL Record Layer units, there'd be none of that fractional state saving
> > going on.
>
> Actually it would, because *record* boundaries and handshake *message*
> boundaries or alert boundaries need not be aligned, and data of the
> various records layer content types may even be interleaved.
Thanks for pointing that out. Guess I need to learn a bit more about SSL
before I open my mouth again.
> Actually both of them, ssl2_peek and ssl3_peek, appear to be broken
> (in different ways), and should be fixed. I must have missed the
> bug report, although I now found that you already reported it at
> least twice.
Thanks for looking into it.
- Dan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
