Cisco Cisco MediaSense Release 9.1(1) Licensing Information

Page of 6316
             Open Source Used In Cisco MediaSense 11.5(1)                                                                                                                                    3096
 
OpenSSL http://www.openssl.org/source/license.html
 
       (May be used for SSL/TLS support) Uses an Original BSD-style license
       with an announcement clause that makes it "incompatible" with GPL. You
       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 or yassl
       instead.
 
GnuTLS  http://www.gnutls.org/
 
       (May be used for SSL/TLS support) Uses the LGPL[3] license. If this is
       a problem for you, consider using OpenSSL instead. Also note that
       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.
 
NSS     http://www.mozilla.org/projects/security/pki/nss/
 
       (May be used for SSL/TLS support) Is covered by the MPL[4] license,
       the GPL[1] license and the LGPL[3] license. You may choose to license
       the code under MPL terms, GPL terms, or LGPL terms. These licenses
       grant you different permissions and impose different obligations. You
       should select the license that best meets your needs.
 
c-ares  http://daniel.haxx.se/projects/c-ares/license.html
 
       (Used for asynchronous name resolves) Uses an MIT license that is very
       liberal and imposes no restrictions on any other library or part you
       may link with.
 
zlib    http://www.gzip.org/zlib/zlib_license.html
 
       (Used for compressed Transfer-Encoding support) Uses an MIT-style
       license that shouldn't collide with any other library.
 
krb4
 
       While nothing in particular says that a Kerberos4 library must use any
       particular license, the one I've tried and used successfully so far
       (kth-krb4) is partly Original BSD-licensed with the announcement
       clause. Some of the code in libcurl that is written to deal with