<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello!<div class=""><br class=""></div><div class="">I have few questions related to openssl distribution.</div><div class=""><br class=""></div><div class="">Let's say that I need this:</div><div class=""><br class=""></div><div class=""><a href="https://pastebin.com/D4Eh0i6P" class="">https://pastebin.com/D4Eh0i6P</a></div><div class=""><br class=""></div><div class="">For my application to keep working.</div><div class=""><br class=""></div><div class="">Could someone please help me with these questions?</div><div class=""><br class=""></div><div class=""><ol class="MailOutline"><li class="">Is that ok to apply this patch to my openssl library and ship it with application (in binary form)?</li><li class="">Is this a license violation, if I do so?</li><li class="">Do I need to mention my changes and share them with users?</li><li class="">May this patch lead to issues for users of my application under any conditions? I.e. does it mean that patching openssl is a security violation?</li><li class="">Is that possible to achieve the same result without openssl source code modification, by configuration flags.</li><li class="">If it is not possible, is that an issue to create a pull request and propose to make these options configurable?</li></ol><div class=""><br class=""></div><div class="">Please, consider that I am trying to avoid openssl source modification.</div><div class=""><br class=""></div><div class="">Kindly appreciate answers for my questions.</div></div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div><div class="">/Dmitriy</div></body></html>