<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I’ve been wondering if an option to build the legacy provider into libcrypto (like the null and default providers) is worthwhile.<div class=""><br class=""></div><div class="">Given this conservation, it seems it might be.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Pauli<br class=""><div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); 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; text-decoration: none;">-- <br class="">Dr Paul Dale | Distinguished Architect | Cryptographic Foundations <br class="">Phone +61 7 3031 7217<br class="">Oracle Australia</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); 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; text-decoration: none;"><br class=""></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 2 May 2020, at 5:30 pm, Richard Levitte <<a href="mailto:levitte@openssl.org" class="">levitte@openssl.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Fri, 01 May 2020 19:22:13 +0200,<br class="">Salz, Rich via openssl-users wrote:<br class=""><blockquote type="cite" class=""><br class="">Hm, so DSO support is a requirement for legacy crypto now? That<br class="">probably needs to be made explicit, and see if the project gets<br class="">pushback.<br class=""></blockquote><br class="">No. When DSO support is turned off, the legacy provider code becomes<br class="">part of libcrypto, in an inaccessible state (in other words, you still<br class="">have to "load" it).<br class=""><br class="">Cheers,<br class="">Richard<br class=""><br class="">-- <br class="">Richard Levitte <a href="mailto:levitte@openssl.org" class="">levitte@openssl.org</a><br class="">OpenSSL Project <a href="http://www.openssl.org/~levitte/" class="">http://www.openssl.org/~levitte/</a><br class=""></div></div></blockquote></div><br class=""></div></body></html>