➜

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 asvetlov, brandon-rhodes, christian.heimes, dstufft, giampaolo.rodola, jcea, jgehrcke, kristjan.jonsson, martius, njs, orsenthil, pitrou
Date 2017-12-01.09:40:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <52c269d0-2418-24e5-36d1-90a69a208bcf@free.fr>
In-reply-to <1512120334.7.0.213398074469.issue16487@psf.upfronthosting.co.za>
Content 
Is it possible to have a single C function that loads the certificates
from memory, or would that make the file-loading case less secure?

Le 01/12/2017 à 10:25, Christian Heimes a écrit :
> 
> Christian Heimes <lists@cheimes.de> added the comment:
> 
> Correct, PEP 543 won't land in Python 3.7 because neither me nor Cory have the resources to land it. However I want all changes and new additions to the SSL module to follow PEP 543 so I can provide a PEP 543-compatible interface in the near future (3.8 or 3.9). We need a proper certificate class anyway to address other issues and feature requests. I don't want to have three ways to load certificates, especially when it involves more C code.
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue16487>
> _______________________________________
>
History
Date User Action Args
2017-12-01 09:40:50pitrousetrecipients: + pitrou, jcea, orsenthil, kristjan.jonsson, giampaolo.rodola, christian.heimes, njs, asvetlov, jgehrcke, brandon-rhodes, dstufft, martius
2017-12-01 09:40:50pitroulinkissue16487 messages
2017-12-01 09:40:50pitroucreate