OpenSSL source modification

Shamatrin Dmitriy justnoxx at gmail.com
Fri Dec 13 16:46:32 UTC 2019


Hello!

I have few questions related to openssl distribution.

Let's say that I need this:

https://pastebin.com/D4Eh0i6P <https://pastebin.com/D4Eh0i6P>

For my application to keep working.

Could someone please help me with these questions?

Is that ok to apply this patch to my openssl library and ship it with application (in binary form)?
Is this a license violation, if I do so?
Do I need to mention my changes and share them with users?
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?
Is that possible to achieve the same result without openssl source code modification, by configuration flags.
If it is not possible, is that an issue to create a pull request and propose to make these options configurable?

Please, consider that I am trying to avoid openssl source modification.

Kindly appreciate answers for my questions.

Thanks.

/Dmitriy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20191213/65c60ad1/attachment.html>


More information about the openssl-users mailing list