Cisco Cisco Firepower Management Center 4000 ライセンス情報

Open Source Used In Firepower System Version 6.1

2096

library. If this is what you want to do, use the GNU Lesser General

Public License instead of this License.

4.30 curl 7.32.0

4.30.1 Available under license :

Permission to use, copy, modify, and distribute this software for any purpose

with or without fee is hereby granted, provided that the above copyright

notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN

NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,

DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR

OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE

OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not

be used in advertising or otherwise to promote the sale, use or other dealings

in this Software without prior written authorization of the copyright holder.

License Mixing with apps, libcurl and Third Party Libraries

===========================================================

libcurl can be built to use a fair amount of various third party libraries,

libraries that are written and provided by other parties that are distributed

using their own licenses. Even libcurl itself contains code that may cause

problems to some. This document attempts to describe what licenses libcurl and

the other libraries use and what possible dilemmas linking and mixing them all

can lead to for end users.

I am not a lawyer and this is not legal advice!

One common dilemma is that GPL[1]-licensed code is not allowed to be linked

with code licensed under the Original BSD license (with the announcement

clause). You may still build your own copies that use them all, but

distributing them as binaries would be to violate the GPL license - unless you

accompany your license with an exception[2]. This particular problem was

addressed when the Modified BSD license was created, which does not have the

announcement clause that collides with GPL.