Cisco Cisco MediaSense Release 9.1(1) Información de licencia

       grant you different permissions and impose different obligations. You

       should select the license that best meets your needs.

 

axTLS   http://axtls.sourceforge.net/

 

       (May be used for SSL/TLS support) Uses a Modified BSD-style license.

 

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

       Kerberos4 is Modified BSD-licensed.

 

MIT Kerberos http://web.mit.edu/kerberos/www/dist/

 

       (May be used for GSS support) MIT licensed, that shouldn't collide

       with any other parts.

 

Heimdal http://www.pdc.kth.se/heimdal/

 

       (May be used for GSS support) Heimdal is Original BSD licensed with

       the announcement clause.

 

GNU GSS http://www.gnu.org/software/gss/

 

       (May be used for GSS support) GNU GSS is GPL licensed. Note that you

       may not distribute binary curl packages that uses this if you build

       curl to also link and use any Original BSD licensed libraries!

 

fbopenssl

 

       (Used for SPNEGO support) Unclear license. Based on its name, I assume

       that it uses the OpenSSL license and thus shares the same issues as

       described for OpenSSL above.