In message <[EMAIL PROTECTED]> on Thu, 13 Oct 2005 11:15:33 +0500, "ahmad hassan" <[EMAIL PROTECTED]> said:
guideveloper123> I am using OpenSSL as a static library with my guideveloper123> proprietary software for windows OS. I would like to guideveloper123> know what steps exactly i have to do pertaining to guideveloper123> licensing to link statically against openssl guideveloper123> library. Have you read the license file (LICENSE)? It's a dual license, and you must heed item 3 from both the "OpenSSL License" and the "Original SSLeay License". Other than that, just don't include "OpenSSL" in your product name (item 5 in "OpenSSL License") and don't use "OpenSSL Toolkit" or "OpenSSL Project" to endorse or promote your product (item 4 in "OpenSSL License") and you'll be fine. Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
