This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vitaly.krug
Recipients christian.heimes, martin.panter, njs, vitaly.krug
Date 2018-03-14.05:41:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521006078.9.0.467229070634.issue33062@psf.upfronthosting.co.za>
In-reply-to
Content
> For extra fun, openssl itself doesn't fully support renegotiation on duplex connections ...

The necessitated modification to the application protocol on that thread sounds like an OpenSSL cop-out. There is no good reason that OpenSSL shouldn't be able to cache incoming application data during the client-initiated handshake just as it does at other times. It should be able to cache the incoming pre-negotiation records, decoding them. The pending() check would inform the client that they need to reap the incoming data during the handshake too.
History
Date User Action Args
2018-03-14 05:41:18vitaly.krugsetrecipients: + vitaly.krug, christian.heimes, njs, martin.panter
2018-03-14 05:41:18vitaly.krugsetmessageid: <1521006078.9.0.467229070634.issue33062@psf.upfronthosting.co.za>
2018-03-14 05:41:18vitaly.kruglinkissue33062 messages
2018-03-14 05:41:18vitaly.krugcreate