Message190743
| Author |
exarkun |
| Recipients |
christian.heimes, eric.araujo, exarkun, pitrou |
| Date |
2013年06月07日.11:47:29 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1370605649.68.0.0307377559609.issue17134@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Sounds promising. Do you think this should be hooked into SSLContext.set_default_verify_paths, or be exposed as a separate method?
If there were an API which exposed the certificate material, then this would be more useful to libraries trying to do other things (present debugging information, use an alternate SSL implementation *wink*, etc). If this is *only* wrapped up inside set_default_verify_paths then many of these extra things are impossible with a seconding binding to the same API. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年06月07日 11:47:29 | exarkun | set | recipients:
+ exarkun, pitrou, christian.heimes, eric.araujo |
| 2013年06月07日 11:47:29 | exarkun | set | messageid: <1370605649.68.0.0307377559609.issue17134@psf.upfronthosting.co.za> |
| 2013年06月07日 11:47:29 | exarkun | link | issue17134 messages |
| 2013年06月07日 11:47:29 | exarkun | create |
|