Hi,
I am asking for clarification more than anything else. Given that I am
not intending to redistribute OpenSSL or modify the OpenSSL
library at all, could you explain some of the terms I've found confusing
in the openssl license?
1) What constitutes "use"? static linking, dynamic linking, runtime
linking using dlopen(), all of the above?
2) Is the process space boundry the limit of "use", as it is for the
GPL?
3) If an application (A) uses a proxy executable (B) for SSL
communications, and B links with openssl and conforms to the openssl
license. Must A still conform, even if the OpenSSL lib is never loaded
into A's address space? What if A and B are distributed in the same
project?
3) Does "this software" in the excerpt from the OpenSSL LICENSE file
below mean OpenSSL or the software which is using OpenSSL? Does
"features" below mean only things which are related to SSL or Crypto
features?
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL
Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
Any help you could give would be appreciated.
I would like to use OpenSSL, versus say NSS, simply because it is a
more established code base and is already installed on many systems.
However, I need to understand the definitions of "use" and "linking" in
the OpenSSL license before I can proceed.
Right now I have proxy code written, which keeps OpenSSL code out
of the library proper. However this is slow and hackish, I would like
some
way where applications could use my library, linking in OpenSSL to their
address space, but not being forced to conform to the advertising
clause.
Thanks,
-Alex
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
