Message 193603 - Python tracker

➜

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	christian.heimes, mpb, pitrou, r.david.murray, underrun
Date	2013-07-23.14:00:34
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
getpeercert() has a crappy API to begin with, but we can't change its behaviour for fear of breaking existing code (and, even, breaking it security-wise). Adding a parameter would make the API even more awful. Which is why I support Christian's idea of exposing a new API, either: - to expose the full cert chain (even if not validated) - or to set the cert verify callback

getpeercert() has a crappy API to begin with, but we can't change its behaviour for fear of breaking existing code (and, even, breaking it security-wise). Adding a parameter would make the API even more awful.

Which is why I support Christian's idea of exposing a new API, either:
- to expose the full cert chain (even if not validated)
- or to set the cert verify callback

History
Date	User	Action	Args
2013-07-23 14:00:35	pitrou	set	recipients: + pitrou, christian.heimes, r.david.murray, underrun, mpb
2013-07-23 14:00:35	pitrou	set	messageid: <[email protected]>
2013-07-23 14:00:35	pitrou	link	issue18293 messages
2013-07-23 14:00:34	pitrou	create