kris
/
boringssl
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2202 Commits
12 Branches
38 MiB
 
 
 
 
 
 
Tree: 95219feafd
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '95219feafd'
${ noResults }
boringssl/LICENSE

186 lines
8.9 KiB
Raw Blame History 

  1. BoringSSL is a fork of OpenSSL. As such, large parts of it fall under OpenSSL

  2. licensing. Files that are completely new have a Google copyright and an ISC

  3. license. This license is reproduced at the bottom of this file.

  4. 

  5. Contributors to BoringSSL are required to follow the CLA rules for Chromium:

  6. https://cla.developers.google.com/clas

  7. 

  8. Some files from Intel are under yet another license, which is also included

  9. underneath.

  10. 

  11. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the

  12. OpenSSL License and the original SSLeay license apply to the toolkit. See below

  13. for the actual license texts. Actually both licenses are BSD-style Open Source

  14. licenses. In case of any license issues related to OpenSSL please contact

  15. openssl-core@openssl.org.

  16. 

  17.   OpenSSL License

  18.   ---------------

  19. 

  20. /* ====================================================================

  21.  * Copyright (c) 1998-2011 The OpenSSL Project.  All rights reserved.

  22.  *

  23.  * Redistribution and use in source and binary forms, with or without

  24.  * modification, are permitted provided that the following conditions

  25.  * are met:

  26.  *

  27.  * 1. Redistributions of source code must retain the above copyright

  28.  *    notice, this list of conditions and the following disclaimer. 

  29.  *

  30.  * 2. Redistributions in binary form must reproduce the above copyright

  31.  *    notice, this list of conditions and the following disclaimer in

  32.  *    the documentation and/or other materials provided with the

  33.  *    distribution.

  34.  *

  35.  * 3. All advertising materials mentioning features or use of this

  36.  *    software must display the following acknowledgment:

  37.  *    "This product includes software developed by the OpenSSL Project

  38.  *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

  39.  *

  40.  * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

  41.  *    endorse or promote products derived from this software without

  42.  *    prior written permission. For written permission, please contact

  43.  *    openssl-core@openssl.org.

  44.  *

  45.  * 5. Products derived from this software may not be called "OpenSSL"

  46.  *    nor may "OpenSSL" appear in their names without prior written

  47.  *    permission of the OpenSSL Project.

  48.  *

  49.  * 6. Redistributions of any form whatsoever must retain the following

  50.  *    acknowledgment:

  51.  *    "This product includes software developed by the OpenSSL Project

  52.  *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"

  53.  *

  54.  * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

  55.  * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

  56.  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

  57.  * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR

  58.  * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

  59.  * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

  60.  * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

  61.  * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

  62.  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

  63.  * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

  64.  * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

  65.  * OF THE POSSIBILITY OF SUCH DAMAGE.

  66.  * ====================================================================

  67.  *

  68.  * This product includes cryptographic software written by Eric Young

  69.  * (eay@cryptsoft.com).  This product includes software written by Tim

  70.  * Hudson (tjh@cryptsoft.com).

  71.  *

  72.  */

  73. 

  74.  Original SSLeay License

  75.  -----------------------

  76. 

  77. /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

  78.  * All rights reserved.

  79.  *

  80.  * This package is an SSL implementation written

  81.  * by Eric Young (eay@cryptsoft.com).

  82.  * The implementation was written so as to conform with Netscapes SSL.

  83.  * 

  84.  * This library is free for commercial and non-commercial use as long as

  85.  * the following conditions are aheared to.  The following conditions

  86.  * apply to all code found in this distribution, be it the RC4, RSA,

  87.  * lhash, DES, etc., code; not just the SSL code.  The SSL documentation

  88.  * included with this distribution is covered by the same copyright terms

  89.  * except that the holder is Tim Hudson (tjh@cryptsoft.com).

  90.  * 

  91.  * Copyright remains Eric Young's, and as such any Copyright notices in

  92.  * the code are not to be removed.

  93.  * If this package is used in a product, Eric Young should be given attribution

  94.  * as the author of the parts of the library used.

  95.  * This can be in the form of a textual message at program startup or

  96.  * in documentation (online or textual) provided with the package.

  97.  * 

  98.  * Redistribution and use in source and binary forms, with or without

  99.  * modification, are permitted provided that the following conditions

  100.  * are met:

  101.  * 1. Redistributions of source code must retain the copyright

  102.  *    notice, this list of conditions and the following disclaimer.

  103.  * 2. Redistributions in binary form must reproduce the above copyright

  104.  *    notice, this list of conditions and the following disclaimer in the

  105.  *    documentation and/or other materials provided with the distribution.

  106.  * 3. All advertising materials mentioning features or use of this software

  107.  *    must display the following acknowledgement:

  108.  *    "This product includes cryptographic software written by

  109.  *     Eric Young (eay@cryptsoft.com)"

  110.  *    The word 'cryptographic' can be left out if the rouines from the library

  111.  *    being used are not cryptographic related :-).

  112.  * 4. If you include any Windows specific code (or a derivative thereof) from 

  113.  *    the apps directory (application code) you must include an acknowledgement:

  114.  *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

  115.  * 

  116.  * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

  117.  * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

  118.  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

  119.  * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

  120.  * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

  121.  * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

  122.  * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

  123.  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

  124.  * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

  125.  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

  126.  * SUCH DAMAGE.

  127.  * 

  128.  * The licence and distribution terms for any publically available version or

  129.  * derivative of this code cannot be changed.  i.e. this code cannot simply be

  130.  * copied and put under another distribution licence

  131.  * [including the GNU Public Licence.]

  132.  */

  133. 

  134. 

  135. ISC license used for completely new code in BoringSSL:

  136. 

  137. /* Copyright (c) 2015, Google Inc.

  138.  *

  139.  * Permission to use, copy, modify, and/or distribute this software for any

  140.  * purpose with or without fee is hereby granted, provided that the above

  141.  * copyright notice and this permission notice appear in all copies.

  142.  *

  143.  * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES

  144.  * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF

  145.  * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY

  146.  * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES

  147.  * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION

  148.  * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN

  149.  * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */

  150. 

  151. 

  152. Some files from Intel carry the following license:

  153. 

  154. # Copyright (c) 2012, Intel Corporation

  155. #

  156. # All rights reserved.

  157. #

  158. # Redistribution and use in source and binary forms, with or without

  159. # modification, are permitted provided that the following conditions are

  160. # met:

  161. #

  162. # *  Redistributions of source code must retain the above copyright

  163. #    notice, this list of conditions and the following disclaimer.

  164. #

  165. # *  Redistributions in binary form must reproduce the above copyright

  166. #    notice, this list of conditions and the following disclaimer in the

  167. #    documentation and/or other materials provided with the

  168. #    distribution.

  169. #

  170. # *  Neither the name of the Intel Corporation nor the names of its

  171. #    contributors may be used to endorse or promote products derived from

  172. #    this software without specific prior written permission.

  173. #

  174. #

  175. # THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION ""AS IS"" AND ANY

  176. # EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

  177. # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

  178. # PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION OR

  179. # CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

  180. # EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

  181. # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

  182. # PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

  183. # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

  184. # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

  185. # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.