1BoringSSL is a fork of OpenSSL. As such, large parts of it fall under OpenSSL 2licensing. Files that are completely new have a Google copyright and an ISC 3license. This license is reproduced at the bottom of this file. 4 5Contributors to BoringSSL are required to follow the CLA rules for Chromium: 6https://cla.developers.google.com/clas 7 8The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the 9OpenSSL License and the original SSLeay license apply to the toolkit. See below 10for the actual license texts. Actually both licenses are BSD-style Open Source 11licenses. In case of any license issues related to OpenSSL please contact 12openssl-core@openssl.org. 13 14 OpenSSL License 15 --------------- 16 17/* ==================================================================== 18 * Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved. 19 * 20 * Redistribution and use in source and binary forms, with or without 21 * modification, are permitted provided that the following conditions 22 * are met: 23 * 24 * 1. Redistributions of source code must retain the above copyright 25 * notice, this list of conditions and the following disclaimer. 26 * 27 * 2. Redistributions in binary form must reproduce the above copyright 28 * notice, this list of conditions and the following disclaimer in 29 * the documentation and/or other materials provided with the 30 * distribution. 31 * 32 * 3. All advertising materials mentioning features or use of this 33 * software must display the following acknowledgment: 34 * "This product includes software developed by the OpenSSL Project 35 * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 36 * 37 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to 38 * endorse or promote products derived from this software without 39 * prior written permission. For written permission, please contact 40 * openssl-core@openssl.org. 41 * 42 * 5. Products derived from this software may not be called "OpenSSL" 43 * nor may "OpenSSL" appear in their names without prior written 44 * permission of the OpenSSL Project. 45 * 46 * 6. Redistributions of any form whatsoever must retain the following 47 * acknowledgment: 48 * "This product includes software developed by the OpenSSL Project 49 * for use in the OpenSSL Toolkit (http://www.openssl.org/)" 50 * 51 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY 52 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 53 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 54 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR 55 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 56 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 57 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 58 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 59 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 60 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 61 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 62 * OF THE POSSIBILITY OF SUCH DAMAGE. 63 * ==================================================================== 64 * 65 * This product includes cryptographic software written by Eric Young 66 * (eay@cryptsoft.com). This product includes software written by Tim 67 * Hudson (tjh@cryptsoft.com). 68 * 69 */ 70 71 Original SSLeay License 72 ----------------------- 73 74/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) 75 * All rights reserved. 76 * 77 * This package is an SSL implementation written 78 * by Eric Young (eay@cryptsoft.com). 79 * The implementation was written so as to conform with Netscapes SSL. 80 * 81 * This library is free for commercial and non-commercial use as long as 82 * the following conditions are aheared to. The following conditions 83 * apply to all code found in this distribution, be it the RC4, RSA, 84 * lhash, DES, etc., code; not just the SSL code. The SSL documentation 85 * included with this distribution is covered by the same copyright terms 86 * except that the holder is Tim Hudson (tjh@cryptsoft.com). 87 * 88 * Copyright remains Eric Young's, and as such any Copyright notices in 89 * the code are not to be removed. 90 * If this package is used in a product, Eric Young should be given attribution 91 * as the author of the parts of the library used. 92 * This can be in the form of a textual message at program startup or 93 * in documentation (online or textual) provided with the package. 94 * 95 * Redistribution and use in source and binary forms, with or without 96 * modification, are permitted provided that the following conditions 97 * are met: 98 * 1. Redistributions of source code must retain the copyright 99 * notice, this list of conditions and the following disclaimer. 100 * 2. Redistributions in binary form must reproduce the above copyright 101 * notice, this list of conditions and the following disclaimer in the 102 * documentation and/or other materials provided with the distribution. 103 * 3. All advertising materials mentioning features or use of this software 104 * must display the following acknowledgement: 105 * "This product includes cryptographic software written by 106 * Eric Young (eay@cryptsoft.com)" 107 * The word 'cryptographic' can be left out if the rouines from the library 108 * being used are not cryptographic related :-). 109 * 4. If you include any Windows specific code (or a derivative thereof) from 110 * the apps directory (application code) you must include an acknowledgement: 111 * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" 112 * 113 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND 114 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 115 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 116 * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 117 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 118 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 119 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 120 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 121 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 122 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 123 * SUCH DAMAGE. 124 * 125 * The licence and distribution terms for any publically available version or 126 * derivative of this code cannot be changed. i.e. this code cannot simply be 127 * copied and put under another distribution licence 128 * [including the GNU Public Licence.] 129 */ 130 131 132ISC license used for completely new code in BoringSSL: 133 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