LICENSE 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218
  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. Contributors to BoringSSL are required to follow the CLA rules for Chromium:
  5. https://cla.developers.google.com/clas
  6. Some files from Intel are under yet another license, which is also included
  7. underneath. Files in third_party/ have their own licenses, as described
  8. therein. The MIT license, for third_party/fiat, which, unlike other third_party
  9. directories, is compiled into non-test libraries, is included below.
  10. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the
  11. OpenSSL License and the original SSLeay license apply to the toolkit. See below
  12. for the actual license texts. Actually both licenses are BSD-style Open Source
  13. licenses. In case of any license issues related to OpenSSL please contact
  14. openssl-core@openssl.org.
  15. The following are Google-internal bug numbers where explicit permission from
  16. some authors is recorded for use of their work. (This is purely for our own
  17. record keeping.)
  18. 27287199
  19. 27287880
  20. 27287883
  21. OpenSSL License
  22. ---------------
  23. /* ====================================================================
  24. * Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
  25. *
  26. * Redistribution and use in source and binary forms, with or without
  27. * modification, are permitted provided that the following conditions
  28. * are met:
  29. *
  30. * 1. Redistributions of source code must retain the above copyright
  31. * notice, this list of conditions and the following disclaimer.
  32. *
  33. * 2. Redistributions in binary form must reproduce the above copyright
  34. * notice, this list of conditions and the following disclaimer in
  35. * the documentation and/or other materials provided with the
  36. * distribution.
  37. *
  38. * 3. All advertising materials mentioning features or use of this
  39. * software must display the following acknowledgment:
  40. * "This product includes software developed by the OpenSSL Project
  41. * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
  42. *
  43. * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
  44. * endorse or promote products derived from this software without
  45. * prior written permission. For written permission, please contact
  46. * openssl-core@openssl.org.
  47. *
  48. * 5. Products derived from this software may not be called "OpenSSL"
  49. * nor may "OpenSSL" appear in their names without prior written
  50. * permission of the OpenSSL Project.
  51. *
  52. * 6. Redistributions of any form whatsoever must retain the following
  53. * acknowledgment:
  54. * "This product includes software developed by the OpenSSL Project
  55. * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
  56. *
  57. * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
  58. * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  59. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  60. * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
  61. * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  62. * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  63. * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  64. * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  65. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
  66. * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  67. * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
  68. * OF THE POSSIBILITY OF SUCH DAMAGE.
  69. * ====================================================================
  70. *
  71. * This product includes cryptographic software written by Eric Young
  72. * (eay@cryptsoft.com). This product includes software written by Tim
  73. * Hudson (tjh@cryptsoft.com).
  74. *
  75. */
  76. Original SSLeay License
  77. -----------------------
  78. /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
  79. * All rights reserved.
  80. *
  81. * This package is an SSL implementation written
  82. * by Eric Young (eay@cryptsoft.com).
  83. * The implementation was written so as to conform with Netscapes SSL.
  84. *
  85. * This library is free for commercial and non-commercial use as long as
  86. * the following conditions are aheared to. The following conditions
  87. * apply to all code found in this distribution, be it the RC4, RSA,
  88. * lhash, DES, etc., code; not just the SSL code. The SSL documentation
  89. * included with this distribution is covered by the same copyright terms
  90. * except that the holder is Tim Hudson (tjh@cryptsoft.com).
  91. *
  92. * Copyright remains Eric Young's, and as such any Copyright notices in
  93. * the code are not to be removed.
  94. * If this package is used in a product, Eric Young should be given attribution
  95. * as the author of the parts of the library used.
  96. * This can be in the form of a textual message at program startup or
  97. * in documentation (online or textual) provided with the package.
  98. *
  99. * Redistribution and use in source and binary forms, with or without
  100. * modification, are permitted provided that the following conditions
  101. * are met:
  102. * 1. Redistributions of source code must retain the copyright
  103. * notice, this list of conditions and the following disclaimer.
  104. * 2. Redistributions in binary form must reproduce the above copyright
  105. * notice, this list of conditions and the following disclaimer in the
  106. * documentation and/or other materials provided with the distribution.
  107. * 3. All advertising materials mentioning features or use of this software
  108. * must display the following acknowledgement:
  109. * "This product includes cryptographic software written by
  110. * Eric Young (eay@cryptsoft.com)"
  111. * The word 'cryptographic' can be left out if the rouines from the library
  112. * being used are not cryptographic related :-).
  113. * 4. If you include any Windows specific code (or a derivative thereof) from
  114. * the apps directory (application code) you must include an acknowledgement:
  115. * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
  116. *
  117. * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
  118. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  119. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  120. * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
  121. * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  122. * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  123. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  124. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  125. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  126. * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  127. * SUCH DAMAGE.
  128. *
  129. * The licence and distribution terms for any publically available version or
  130. * derivative of this code cannot be changed. i.e. this code cannot simply be
  131. * copied and put under another distribution licence
  132. * [including the GNU Public Licence.]
  133. */
  134. ISC license used for completely new code in BoringSSL:
  135. /* Copyright (c) 2015, Google Inc.
  136. *
  137. * Permission to use, copy, modify, and/or distribute this software for any
  138. * purpose with or without fee is hereby granted, provided that the above
  139. * copyright notice and this permission notice appear in all copies.
  140. *
  141. * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
  142. * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
  143. * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
  144. * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
  145. * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
  146. * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
  147. * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */
  148. Some files from Intel carry the following license:
  149. # Copyright (c) 2012, Intel Corporation
  150. #
  151. # All rights reserved.
  152. #
  153. # Redistribution and use in source and binary forms, with or without
  154. # modification, are permitted provided that the following conditions are
  155. # met:
  156. #
  157. # * Redistributions of source code must retain the above copyright
  158. # notice, this list of conditions and the following disclaimer.
  159. #
  160. # * Redistributions in binary form must reproduce the above copyright
  161. # notice, this list of conditions and the following disclaimer in the
  162. # documentation and/or other materials provided with the
  163. # distribution.
  164. #
  165. # * Neither the name of the Intel Corporation nor the names of its
  166. # contributors may be used to endorse or promote products derived from
  167. # this software without specific prior written permission.
  168. #
  169. #
  170. # THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION ""AS IS"" AND ANY
  171. # EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  172. # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  173. # PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION OR
  174. # CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
  175. # EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
  176. # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
  177. # PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
  178. # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
  179. # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
  180. # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  181. The code in third_party/fiat carries the MIT license:
  182. Copyright (c) 2015-2016 the fiat-crypto authors (see
  183. https://github.com/mit-plv/fiat-crypto/blob/master/AUTHORS).
  184. Permission is hereby granted, free of charge, to any person obtaining a copy
  185. of this software and associated documentation files (the "Software"), to deal
  186. in the Software without restriction, including without limitation the rights
  187. to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  188. copies of the Software, and to permit persons to whom the Software is
  189. furnished to do so, subject to the following conditions:
  190. The above copyright notice and this permission notice shall be included in all
  191. copies or substantial portions of the Software.
  192. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  193. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  194. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  195. AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  196. LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  197. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  198. SOFTWARE.