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 njs
Recipients christian.heimes, martin.panter, njs, vitaly.krug
Date 2018-03-14.06:04:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521007451.46.0.467229070634.issue33062@psf.upfronthosting.co.za>
In-reply-to
Content
> an OpenSSL cop-out

Perhaps, but they've been doing it this way for a decade+, and we're living in a time when other libraries like BoringSSL are flat-out removing renegotiation support, so good luck convincing them to fix things. Anyway, it's nothing to do with Python, just a friendly heads-up; I ran into this when trying to do renegotiation tests on my non-blocking code using the 'ssl' module and was *very* confused for a while until I realized it wasn't my code's fault at all.
History
Date User Action Args
2018-03-14 06:04:11njssetrecipients: + njs, christian.heimes, martin.panter, vitaly.krug
2018-03-14 06:04:11njssetmessageid: <1521007451.46.0.467229070634.issue33062@psf.upfronthosting.co.za>
2018-03-14 06:04:11njslinkissue33062 messages
2018-03-14 06:04:11njscreate