Replies: 2 comments 1 reply
-
I can't speak to the copyright issue, but I don't think extracting and re-encoding the archive is the right technical approach here. I think the right thing to do, if your library has a dependency on libcrypto.a is to document that, and require that linking applications link against both your library and libcrypto |
Beta Was this translation helpful? Give feedback.
-
I am not a lawyer and I cannot get you legal advice - you need to consult an actual lawyer for that. AFAIK there are no lawyers likely to look at these discussions - just techies :-) However, I can point you at important parts of the licence and suggestions about what you need to consider. Firstly, what version of OpenSSL are you using? OpenSSL prior to 3.0 comes with different licence terms to 3.0 and above. I will assume you are using 3.0 or above since those are the only versions of OpenSSL currently supported by the project. For 3.0 and above, OpenSSL uses the Apache v2 licence. You can read it here (it also comes bundled with the OpenSSL download): https://www.openssl.org/source/apache-license-2.0.txt The Apache v2 licence grants you a copyright licence to do certain things:
From my limited understanding of what you are doing it sounds like you are preparing a derivative work in object form. You also have certain obligations if you are intending to redistribute your derivative work:
So you must adhere to all of these items in your redistributed work. Most of this is non-technical in nature and doesn't say anything about the nature or form of any derivative work. Given all of the above you need to decide for yourself whether what you are doing complies with the licence. We cannot give you that advice. Of course I've only highlighted some specific sections that seem particularly relevant to your question. It goes without saying that you must adhere to the entire licence text. |
Beta Was this translation helpful? Give feedback.
-
I'm creating a static C library which includes SHA256 encryption from the OpenSSL library. As I couldn't find a way to link my static lib with the
libcrypto.a
(which has the code that I'm using), I unzipped the whole libcrypto.a lib and created a static lib containing my lib and the object files oflibcrypto.a
.Does anyone know if this will violate any copyright laws?
Beta Was this translation helpful? Give feedback.
All reactions