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 mathieui
Recipients gvanrossum, mathieui, pitrou, vstinner, yselivanov
Date 2014-10-30.18:48:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414694911.53.0.838591134906.issue22768@psf.upfronthosting.co.za>
In-reply-to
Content
>I'm not sure that would make a difference. We still have to implement
>the proxy SSLSocket, which is no easier than adding the extra info by
>hand. Or did I misunderstand you?


The difference would be that exposing methods can be more future-proof, as some methods take parameters (like the offender getpeercert(bool), or get_channel_binding() that takes an element of ssl.CHANNEL_BINDING_TYPES, list that may grow in the future) that need to be covered in the properties. But the API of SSLSocket is stable and small so I don't think it really matters.
History
Date User Action Args
2014-10-30 18:48:31mathieuisetrecipients: + mathieui, gvanrossum, pitrou, vstinner, yselivanov
2014-10-30 18:48:31mathieuisetmessageid: <1414694911.53.0.838591134906.issue22768@psf.upfronthosting.co.za>
2014-10-30 18:48:31mathieuilinkissue22768 messages
2014-10-30 18:48:31mathieuicreate