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 | j1m |
|---|---|
| Recipients | gvanrossum, j1m, vstinner, yselivanov |
| Date | 2016年06月29日.18:28:06 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1467224887.26.0.0387344661363.issue27392@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
With SSL, the protocol is a little different clients and servers, although that may just be in the handshake. I'm no SSL expert by any means. When you call wrap_socket on an SSLContext, you can pass server_side, which defaults to False. If you get this wrong, you end up with an SSL protocol error. FWIW, here's my awful monkey patch to work around this experimentally in ZEO: https://github.com/zopefoundation/ZEO/pull/32/commits/daca97cb4292ad9a316a1924960a5fbf54d3622b#diff-248404a51b1503a38c3319c85e6c1c5aR174 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016年06月29日 18:28:07 | j1m | set | recipients: + j1m, gvanrossum, vstinner, yselivanov |
| 2016年06月29日 18:28:07 | j1m | set | messageid: <1467224887.26.0.0387344661363.issue27392@psf.upfronthosting.co.za> |
| 2016年06月29日 18:28:07 | j1m | link | issue27392 messages |
| 2016年06月29日 18:28:06 | j1m | create | |