25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

252 lines
12 KiB

  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. Files in third_party/ have their own licenses, as described therein. The MIT
  7. license, for third_party/fiat, which, unlike other third_party directories, is
  8. compiled into non-test libraries, is included below.
  9. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the
  10. OpenSSL License and the original SSLeay license apply to the toolkit. See below
  11. for the actual license texts. Actually both licenses are BSD-style Open Source
  12. licenses. In case of any license issues related to OpenSSL please contact
  13. openssl-core@openssl.org.
  14. The following are Google-internal bug numbers where explicit permission from
  15. some authors is recorded for use of their work. (This is purely for our own
  16. record keeping.)
  17. 27287199
  18. 27287880
  19. 27287883
  20. OpenSSL License
  21. ---------------
  22. /* ====================================================================
  23. * Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
  24. *
  25. * Redistribution and use in source and binary forms, with or without
  26. * modification, are permitted provided that the following conditions
  27. * are met:
  28. *
  29. * 1. Redistributions of source code must retain the above copyright
  30. * notice, this list of conditions and the following disclaimer.
  31. *
  32. * 2. Redistributions in binary form must reproduce the above copyright
  33. * notice, this list of conditions and the following disclaimer in
  34. * the documentation and/or other materials provided with the
  35. * distribution.
  36. *
  37. * 3. All advertising materials mentioning features or use of this
  38. * software must display the following acknowledgment:
  39. * "This product includes software developed by the OpenSSL Project
  40. * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
  41. *
  42. * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
  43. * endorse or promote products derived from this software without
  44. * prior written permission. For written permission, please contact
  45. * openssl-core@openssl.org.
  46. *
  47. * 5. Products derived from this software may not be called "OpenSSL"
  48. * nor may "OpenSSL" appear in their names without prior written
  49. * permission of the OpenSSL Project.
  50. *
  51. * 6. Redistributions of any form whatsoever must retain the following
  52. * acknowledgment:
  53. * "This product includes software developed by the OpenSSL Project
  54. * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
  55. *
  56. * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
  57. * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  58. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  59. * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
  60. * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  61. * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  62. * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  63. * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  64. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
  65. * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  66. * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
  67. * OF THE POSSIBILITY OF SUCH DAMAGE.
  68. * ====================================================================
  69. *
  70. * This product includes cryptographic software written by Eric Young
  71. * (eay@cryptsoft.com). This product includes software written by Tim
  72. * Hudson (tjh@cryptsoft.com).
  73. *
  74. */
  75. Original SSLeay License
  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. ISC license used for completely new code in BoringSSL:
  134. /* Copyright (c) 2015, Google Inc.
  135. *
  136. * Permission to use, copy, modify, and/or distribute this software for any
  137. * purpose with or without fee is hereby granted, provided that the above
  138. * copyright notice and this permission notice appear in all copies.
  139. *
  140. * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
  141. * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
  142. * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
  143. * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
  144. * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
  145. * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
  146. * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */
  147. The code in third_party/fiat carries the MIT license:
  148. Copyright (c) 2015-2016 the fiat-crypto authors (see
  149. https://github.com/mit-plv/fiat-crypto/blob/master/AUTHORS).
  150. Permission is hereby granted, free of charge, to any person obtaining a copy
  151. of this software and associated documentation files (the "Software"), to deal
  152. in the Software without restriction, including without limitation the rights
  153. to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  154. copies of the Software, and to permit persons to whom the Software is
  155. furnished to do so, subject to the following conditions:
  156. The above copyright notice and this permission notice shall be included in all
  157. copies or substantial portions of the Software.
  158. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  159. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  160. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  161. AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  162. LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  163. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  164. SOFTWARE.
  165. Licenses for support code
  166. -------------------------
  167. Parts of the TLS test suite are under the Go license. This code is not included
  168. in BoringSSL (i.e. libcrypto and libssl) when compiled, however, so
  169. distributing code linked against BoringSSL does not trigger this license:
  170. Copyright (c) 2009 The Go Authors. All rights reserved.
  171. Redistribution and use in source and binary forms, with or without
  172. modification, are permitted provided that the following conditions are
  173. met:
  174. * Redistributions of source code must retain the above copyright
  175. notice, this list of conditions and the following disclaimer.
  176. * Redistributions in binary form must reproduce the above
  177. copyright notice, this list of conditions and the following disclaimer
  178. in the documentation and/or other materials provided with the
  179. distribution.
  180. * Neither the name of Google Inc. nor the names of its
  181. contributors may be used to endorse or promote products derived from
  182. this software without specific prior written permission.
  183. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  184. "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
  185. LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
  186. A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
  187. OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  188. SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
  189. LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
  190. DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
  191. THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  192. (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  193. OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  194. BoringSSL uses the Chromium test infrastructure to run a continuous build,
  195. trybots etc. The scripts which manage this, and the script for generating build
  196. metadata, are under the Chromium license. Distributing code linked against
  197. BoringSSL does not trigger this license.
  198. Copyright 2015 The Chromium Authors. All rights reserved.
  199. Redistribution and use in source and binary forms, with or without
  200. modification, are permitted provided that the following conditions are
  201. met:
  202. * Redistributions of source code must retain the above copyright
  203. notice, this list of conditions and the following disclaimer.
  204. * Redistributions in binary form must reproduce the above
  205. copyright notice, this list of conditions and the following disclaimer
  206. in the documentation and/or other materials provided with the
  207. distribution.
  208. * Neither the name of Google Inc. nor the names of its
  209. contributors may be used to endorse or promote products derived from
  210. this software without specific prior written permission.
  211. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  212. "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
  213. LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
  214. A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
  215. OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  216. SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
  217. LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
  218. DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
  219. THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  220. (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  221. OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.