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 pitrou
Recipients Arfrever, dlmiles, flox, giampaolo.rodola, janssen, jcea, pitrou, vstinner
Date 2010-04-16.19:32:01
SpamBayes Score 1.180383e-08
Marked as misclassified No
Message-id <1271446326.5.0.875614654684.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
After thinking a bit about it, we're in quasi-feature freeze now for 2.x and it doesn't sound reasonable to add options to unwrap(); we would need to write tests to exercise these options and their behaviour. Also, they aren't strictly needed to fix the issues at hand, but provide a functional benefit.

So I've taken some of Darryl's ideas and fixes and incorporated them. Here is a new patch with them. I've checked compatibility with OpenSSL 1.0.0 and 0.9.8k. If nobody manifests him/herself I will commit it soon.

(note: I dropped the idea of checking for application data with SSL_peek(), since it seems to be a blocking call; at least one of the test_ssl test cases froze here)
History
Date User Action Args
2010-04-16 19:32:07pitrousetrecipients: + pitrou, jcea, janssen, vstinner, giampaolo.rodola, Arfrever, flox, dlmiles
2010-04-16 19:32:06pitrousetmessageid: <1271446326.5.0.875614654684.issue8108@psf.upfronthosting.co.za>
2010-04-16 19:32:05pitroulinkissue8108 messages
2010-04-16 19:32:04pitroucreate