> My opinion: if you distribute the proxy code as a separate package and
> the rest of your application doesn't call OpenSSL and your proxy and
> application aren't bundled together in one distribution, then you can
> get away with only acknowledging the use of OpenSSL in your proxy
> distribution. This will obviously mean that you will have to tell
> people that your application A requires or recommends the installation
> of yoru proxy B, which will indirectly lead them to the acknowledgment
> of OpenSSL :-).
The OpenSSL license requires that you credit OpenSSL whenever you
mention features of OpenSSL. It is not clear to me why features that another
library obtains directly from OpenSSL, without significant transformation,
aren't features or use of OpenSSL.
It certainly would violate the spirit of the license for me to create a
product that consists of nothing but links to OpenSSL, and then use that
library to claim that I'm mentioning features of it, not OpenSSL, and are
therefore exempt from the advertising clause.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
