Message307320
| Author |
kristjan.jonsson |
| Recipients |
asvetlov, brandon-rhodes, christian.heimes, dstufft, giampaolo.rodola, jcea, jgehrcke, kristjan.jonsson, martius, njs, orsenthil, pitrou |
| Date |
2017年11月30日.15:23:28 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP8kY6bBz681az8Bin7XFGVwSVQw+eMNO3WjBGEZnti-4kcaQw@mail.gmail.com> |
| In-reply-to |
<1512043419.56.0.213398074469.issue16487@psf.upfronthosting.co.za> |
| Content |
OP here, lurking.
The need to load server certificates from memory is quite real. Some seven
years ago I wrote custom code to handle that for CCPs python branch, and
contributed patches to that effect.
It's always dismaying to see how peoples efforts get bogged down by one
thing or another. So, now there is a pep that prohibits this change? Fun
times.
2017年11月30日 12:03 GMT+00:00 Christian Heimes <report@bugs.python.org>:
>
> Christian Heimes <lists@cheimes.de> added the comment:
>
> I'm working on a PEP that builds on top of PEP 543 and addresses some
> issues like IDNA #28414, OpenSSL/LibreSSL compatibility, hostname
> verification, verification chain, and TLS 1.3. As part of the PEP
> implementation, I'll add a certificate class.
>
> I don't to introduce yet another way to load a certificate. The C code is
> already complicated enough.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue16487>
> _______________________________________
> |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年11月30日 15:23:28 | kristjan.jonsson | set | recipients:
+ kristjan.jonsson, jcea, orsenthil, pitrou, giampaolo.rodola, christian.heimes, njs, asvetlov, jgehrcke, brandon-rhodes, dstufft, martius |
| 2017年11月30日 15:23:28 | kristjan.jonsson | link | issue16487 messages |
| 2017年11月30日 15:23:28 | kristjan.jonsson | create |
|