License(GPL) is very restrictive for Commercial Products.

[GoogleCodeExporter]

Can you change the license the license to MIT or BSD?

Original issue reported on code.google.com by [email protected] on 22 Oct 2009 at 9:46

[GoogleCodeExporter]

or LGPL?

Original comment by [email protected] on 26 Jan 2010 at 3:41

[GoogleCodeExporter]

In fact, I believe this statement from OpenSSL/ssleay makes it so this cannot be
distributed under GPL:

"* The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
"

Please understand, I'm very thankful for your work to release this distribution 
of
this project, but as I'm looking to use it for a commercial project, I believe 
that
this is a valid licensing issue.

Thanks for your time!
   Mike

Original comment by [email protected] on 26 Jan 2010 at 3:46

[GoogleCodeExporter]

usage of dynamic library (.so) is a special case, completely different from 
static
link of the library.

If my memory is right, GPL places the restriction on the static linking only.

Original comment by [email protected] on 30 Mar 2010 at 6:11

[GoogleCodeExporter]

the license is simply incorrect...
Compiling some code can't change its license. also the code isn't here.
the author did a great job of compiling the library and packaging it 
beautifully.
you have to mess with it a bit to compile it yourself. but you get the same 
result
from compiling the library yourself.

OpenSSL is under a BSD-style license.
so this is a just great compilation of openssl.
http://www.openssl.org/source/license.html

Original comment by [email protected] on 15 Apr 2010 at 1:11

[GoogleCodeExporter]

Furthermore, GPL license is not distributed nor mentioned in the download.  
Please change the listed project license to reflect the code's true license: 
BSD 

Original comment by [email protected] on 15 Jun 2010 at 4:26

[GoogleCodeExporter]

Also, the OpenSSL FAQ specifically addresses using OpenSSL with other GPL 
software http://www.openssl.org/support/faq.html#LEGAL2

Original comment by [email protected] on 15 Jun 2010 at 4:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

You should definitely fix license stated in project information, to not confuse 
people.

And, I'm sure, you violate OpenSSL license, clause 6:

 * 6. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"

You should place a link and acknowledgment at main page.


Anyway, there are http://slproweb.com/products/Win32OpenSSL.html — regularly 
updated builds of OpenSSL, including 1.0.0 and 1.0.1 branches, for Windows x32 
and x64.

Original comment by basil.peace on 16 Jan 2014 at 7:35