From e5cf6a20a77eeaa3a4b791f29a05dadd54636edb Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 7 Jul 2006 20:48:51 +0000 Subject: yassl can be used now --- RELEASE-NOTES | 2 ++ docs/LICENSE-MIXING | 8 +++++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/RELEASE-NOTES b/RELEASE-NOTES index fa925c6be..06c7d5a34 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -23,6 +23,8 @@ This release includes the following bugfixes: Other curl-related news: + o yassl 1.3.7 can now be used with libcurl as an optional TLS library for + HTTPS/FTPS support o cURLpp 0.6.0 was released: http://rrette.com/curlpp.html o pycurl-7.15.4 was released: http://pycurl.sf.net diff --git a/docs/LICENSE-MIXING b/docs/LICENSE-MIXING index 0cf8a89e7..60f5f934c 100644 --- a/docs/LICENSE-MIXING +++ b/docs/LICENSE-MIXING @@ -32,7 +32,8 @@ OpenSSL http://www.openssl.org/source/license.html are not allowed to ship binaries that link with OpenSSL that includes GPL code (unless that specific GPL code includes an exception for OpenSSL - a habit that is growing more and more common). If OpenSSL's - licensing is a problem for you, consider using GnuTLS instead. + licensing is a problem for you, consider using GnuTLS or yassl + instead. GnuTLS http://www.gnutls.org/ @@ -41,6 +42,11 @@ GnuTLS http://www.gnutls.org/ GnuTLS itself depends on and uses other libs (libgcrypt and libgpg-error) and they too are LGPL- or GPL-licensed. +yassl http://www.yassl.com/ + + (May be used for SSL/TLS support) Uses the GPL[1] license. If this is + a problem for you, consider using OpenSSL or GnuTLS instead. + c-ares http://daniel.haxx.se/projects/c-ares/license.html (Used for asynchronous name resolves) Uses an MIT license that is very -- cgit v1.2.3