<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=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 25, 2020, at 4:09 AM, Joshua Root <<a href="mailto:jmr@macports.org" class="">jmr@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2020-8-25 19:42 , Eric F (iEFdev) wrote:<br class=""><blockquote type="cite" class="">Fedora, who usually are very restricted about things, have this take:<br class=""><br class=""><blockquote type="cite" class="">“ However, we consider that the OpenSSL library is a system library,<br class=""></blockquote>as defined by the GPL, *on Fedora* and therefore we are allowed to ship<br class="">GPL software that links to the OpenSSL library. …”<br class=""><blockquote type="cite" class="">—<br class=""></blockquote><a href="https://fedoraproject.org/wiki/Licensing:FAQ?rd=Licensing/FAQ#What.27s_the_deal_with_the_OpenSSL_license.3F" class="">https://fedoraproject.org/wiki/Licensing:FAQ?rd=Licensing/FAQ#What.27s_the_deal_with_the_OpenSSL_license.3F</a><br class=""></blockquote><br class="">Fedora is an operating system. MacPorts is not. Also worth noting that<br class="">not all distros agree with that interpretation.<br class=""><br class="">- Josh<br class=""></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">There is a new version of openssl coming with a more agreeable license we understand, due this year. That will help, eventually.</div><div class=""><br class=""></div><div class="">But I guess this is why Jeremy changes/fixes everything to build with libressl. I see curl uses libressl with ease. Our “port info” says libressl has the OpenSSL license, but that can’t be quite accurate as otherwise what’s the point?</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">License: OpenSSL and SSLeay</span></div></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><br class=""></div><div class="">It must be tempting for the managers to consider defaulting MacPorts to libressl and solve all this in one fell swoop until openssl fixes itself — seems to me you must have gone round and round and round this before when I wasn’t paying so much attention to it. I presume there is some incompatibility or other compelling problem with that plan.</div><div class=""><br class=""></div><div class="">I noted libressl is actively updated, last release was Aug 17, 2020….</div><div class=""><br class=""></div><div class="">Ken</div></div></body></html>