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 David Ford (FirefighterBlu3)
Recipients David Ford (FirefighterBlu3), christian.heimes, vstinner
Date 2017-02-15.12:10:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487160636.95.0.472983927759.issue29470@psf.upfronthosting.co.za>
In-reply-to
Content
yes, i create a context and then when a request comes in, i load the appropriate key. this is how most [all?] SNI capable python server examples show how to do it, or did, at the time I wrote this module a few years ago. from that time, ~py 3.2 until now, it worked perfectly.

thank you for this information, i'll rewrite my callback accordingly. perhaps 18.2.5.3 in https://docs.python.org/3/library/ssl.html can be updated to inform developers how to change their socket.context in an SNI callback
History
Date User Action Args
2017-02-15 12:10:36David Ford (FirefighterBlu3)setrecipients: + David Ford (FirefighterBlu3), vstinner, christian.heimes
2017-02-15 12:10:36David Ford (FirefighterBlu3)setmessageid: <1487160636.95.0.472983927759.issue29470@psf.upfronthosting.co.za>
2017-02-15 12:10:36David Ford (FirefighterBlu3)linkissue29470 messages
2017-02-15 12:10:36David Ford (FirefighterBlu3)create