➜
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.
Created on 2020-11-11 17:17 by MineRobber9000, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg380776 - (view) | Author: MineRobber___T (MineRobber9000) | Date: 2020-11-11 17:17 | |
The SSL library currently lacks the ability to accept a client certificate without attempting to verify it. To alleviate this issue, I was thinking that an attribute could be added to the ssl.SSLContext class along the lines of `verify_callback` (similar to how the SNI callback is handled) which would allow the implementation of custom cert verification. I'd be willing to help work on this, if I knew where to even begin. |
|||
| msg380788 - (view) | Author: Zackery Spytz (ZackerySpytz) *  |
Date: 2020-11-11 18:58 | |
Unfortunately, this seems like a duplicate of bpo-31242. |
|||
| msg380790 - (view) | Author: Christian Heimes (christian.heimes) *  |
Date: 2020-11-11 19:29 | |
Yes, it's a duplicate. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:38 | admin | set | github: 86492 |
| 2020-11-11 19:29:01 | christian.heimes | set | status: open -> closed resolution: duplicate messages: + msg380790 superseder: Add SSLContext.set_verify_callback() stage: resolved |
| 2020-11-11 18:58:16 | ZackerySpytz | set | nosy:
+ ZackerySpytz messages: + msg380788 |
| 2020-11-11 17:17:51 | MineRobber9000 | create | |