Showing content from http://mail.python.org/pipermail/python-dev/attachments/20170608/eeb0dc77/attachment.html below:
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 8 Jun 2017, at 21:17, Donald Stufft <<a href="mailto:donald@stufft.io" class="">donald@stufft.io</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">On Jun 8, 2017, at 3:57 PM, Steve Dower <<a href="mailto:steve.dower@python.org" class="">steve.dower@python.org</a>> wrote:</div><div class=""><div class=""><br class="">Awesome, this is exactly what I needed to see.<br class=""><br class="">What if Python 2.7 just exposed the OpenSSL primitives necessary so that ctypes could use them? Is that a viable approach here? Presumably then a MemoryBIO backport could be pure-Python.<br class=""><br class="">It doesn't help the other *ythons, but unless they have MemoryBIO implementations ready to backport then I can't think of anything that will help them short of a completely new API.<br class=""><br class=""></div></div></blockquote><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">I would have to let Cory answer the question about feasibility here since heâs much more familiar with OpenSSLâs API (and even binding something like this with ctypes) than I am. The first thing that really stands out to me though is it just feels a bit like shuffling deckchairs?</div></div></blockquote><div><br class=""></div><div>The short answer is that, while itâs do-able, we have some problems with ABI compatibility. OpenSSL 1.1 and 1.0 are ABI incompatible, so I have to write divergent ctypes code to handle each case. It may also be relevant to support OpenSSL 0.9.x so we roll into the same ABI compatibility concern all over again. Doubly annoyingly a bunch of OpenSSL code in 1.0 is actually macros which donât work in ctypes so thereâll be a lot of futzing about in structures to get what I need to do done.</div><div><br class=""></div><div>This also doesnât get into the difficulty of some operating systems shipping a LibreSSL masquerading as an OpenSSL, which is subtly incompatible in ways I donât fully understand at this time.</div></div><br class=""></body></html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4