summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/OpenSSL
diff options
context:
space:
mode:
authorBeth Flanagan <elizabeth.flanagan@intel.com>2011-06-15 13:52:23 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-06-23 23:44:49 +0100
commit7cd2ac0e40d854bab9a32512018aff6172500c0e (patch)
tree99366a7b07db9f0b53bb9d411f0016f36982616d /meta/files/common-licenses/OpenSSL
parent879a7f819b7f38cda82d97489af433310aabfed1 (diff)
downloadpoky-7cd2ac0e40d854bab9a32512018aff6172500c0e.tar.gz
common-licenses: Additions and corrections
I've added more licenses from SPDX and corrected the gcc license so that it is a. parsable and b. accurate to the SPDX standard. I've also done some cleanup of license text and gdb's LICENSE field. (From OE-Core rev: e47343d12ee571281238bbf5663b074c0e32049f) Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/files/common-licenses/OpenSSL')
-rw-r--r--meta/files/common-licenses/OpenSSL212
1 files changed, 98 insertions, 114 deletions
diff --git a/meta/files/common-licenses/OpenSSL b/meta/files/common-licenses/OpenSSL
index e6a1c01677..d4270a3329 100644
--- a/meta/files/common-licenses/OpenSSL
+++ b/meta/files/common-licenses/OpenSSL
@@ -1,123 +1,107 @@
1 1
2OpenSSL License 2OpenSSL License
3 3
4==================================================================== 4 ====================================================================
5Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. 5 Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
6 6
7Redistribution and use in source and binary forms, with or without 7 Redistribution and use in source and binary forms, with or without
8modification, are permitted provided that the following conditions 8 modification, are permitted provided that the following conditions
9are met: 9 are met:
10 10
111. Redistributions of source code must retain the above copyright 11 1. Redistributions of source code must retain the above copyright
12notice, this list of conditions and the following disclaimer. 12 notice, this list of conditions and the following disclaimer.
13 13
142. Redistributions in binary form must reproduce the above copyright 14 2. Redistributions in binary form must reproduce the above copyright
15notice, this list of conditions and the following disclaimer in 15 notice, this list of conditions and the following disclaimer in
16the documentation and/or other materials provided with the 16 the documentation and/or other materials provided with the
17distribution. 17 distribution.
18 18
193. All advertising materials mentioning features or use of this 19 3. All advertising materials mentioning features or use of this
20software must display the following acknowledgment: 20 software must display the following acknowledgment:
21"This product includes software developed by the OpenSSL Project 21 "This product includes software developed by the OpenSSL Project
22for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 22 for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
23 23
244. The names "OpenSSL Toolkit" and "OpenSSL Project" must 24 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
25not be used to 25 endorse or promote products derived from this software without
26endorse or promote products derived from this software without 26 prior written permission. For written permission, please contact
27prior written permission. For written permission, please contact 27 openssl-core@openssl.org.
28openssl-core@openssl.org. 28
29 29 5. Products derived from this software may not be called "OpenSSL"
305. Products derived from this software may not be called "OpenSSL" 30 nor may "OpenSSL" appear in their names without prior written
31nor may "OpenSSL" appear in their names without prior written 31 permission of the OpenSSL Project.
32permission of the OpenSSL Project. 32
33 33 6. Redistributions of any form whatsoever must retain the following
346. Redistributions of any form whatsoever must retain the following 34 acknowledgment:
35acknowledgment: 35 "This product includes software developed by the OpenSSL Project
36"This product includes software developed by the OpenSSL Project 36 for use in the OpenSSL Toolkit (http://www.openssl.org/)"
37for use in the OpenSSL Toolkit (http://www.openssl.org/)" 37
38 38 THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
39THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY 39 EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
40EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 40 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
41IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 41 PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
42PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR 42 ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
43ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 43 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
44SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 44 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
45NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 45 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
46LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 46 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
47HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 47 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
48STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 48 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
49ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 49 OF THE POSSIBILITY OF SUCH DAMAGE.
50OF THE POSSIBILITY OF SUCH DAMAGE. 50 ====================================================================
51==================================================================== 51
52 52 This product includes cryptographic software written by Eric Young
53This product includes cryptographic software written by Eric Young 53 (eay@cryptsoft.com). This product includes software written by Tim
54(eay@cryptsoft.com). This product includes software written by Tim 54 Hudson (tjh@cryptsoft.com).
55Hudson (tjh@cryptsoft.com). 55
56 56
57 57 Original SSLeay License
58Original SSLeay License 58 -----------------------
59-----------------------
60 59
61Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) 60Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
62All rights reserved. 61All rights reserved.
63 62
64This package is an SSL implementation written 63 This package is an SSL implementation written
65by Eric Young (eay@cryptsoft.com). 64 by Eric Young (eay@cryptsoft.com).
66The implementation was written so as to conform with Netscapes SSL. 65 The implementation was written so as to conform with Netscapes SSL.
67 66
68This library is free for commercial and non-commercial use as long as 67 This library is free for commercial and non-commercial use as long as
69the following conditions are aheared to. The following conditions 68 the following conditions are aheared to. The following conditions
70apply to all code found in this distribution, be it the RC4, RSA, 69 apply to all code found in this distribution, be it the RC4, RSA,
71lhash, DES, etc., code; not just the SSL code. The SSL documentation 70 lhash, DES, etc., code; not just the SSL code. The SSL documentation
72included with this distribution is covered by the same copyright terms 71 included with this distribution is covered by the same copyright terms
73except that the holder is Tim Hudson (tjh@cryptsoft.com). 72 except that the holder is Tim Hudson (tjh@cryptsoft.com).
74 73
75Copyright remains Eric Young's, and as such any Copyright notices in 74 Copyright remains Eric Young`s, and as such any Copyright notices in
76the code are not to be removed. 75 the code are not to be removed.
77If this package is used in a product, Eric Young should be given attribution 76 If this package is used in a product, Eric Young should be given attribution
78as the author of the parts of the library used. 77 as the author of the parts of the library used.
79This can be in the form of a textual message at program startup or 78 This can be in the form of a textual message at program startup or
80in documentation (online or textual) provided with the package. 79 in documentation (online or textual) provided with the package.
81 80
82Redistribution and use in source and binary forms, with or without 81 Redistribution and use in source and binary forms, with or without
83modification, are permitted provided that the following conditions 82 modification, are permitted provided that the following conditions
84are met: 83 are met:
851. Redistributions of source code must retain the copyright 84 1. Redistributions of source code must retain the copyright
86notice, this list of conditions and the following disclaimer. 85 notice, this list of conditions and the following disclaimer.
872. Redistributions in binary form must reproduce the above copyright 86 2. Redistributions in binary form must reproduce the above copyright
88notice, this list of conditions and the following disclaimer in the 87 notice, this list of conditions and the following disclaimer in the
89documentation and/or other materials provided with the distribution. 88 documentation and/or other materials provided with the distribution.
903. All advertising materials mentioning features or use of this software 89 3. All advertising materials mentioning features or use of this software
91must display the following acknowledgement: 90 must display the following acknowledgement:
92"This product includes cryptographic software written by 91 "This product includes cryptographic software written by
93Eric Young (eay@cryptsoft.com)" 92 Eric Young (eay@cryptsoft.com)"
94The word 'cryptographic' can be left out if the rouines from the library 93 The word `cryptographic` can be left out if the rouines from the library
95being used are not cryptographic related :-). 94 being used are not cryptographic related :-).
964. If you include any Windows specific code (or a derivative thereof) from 95 4. If you include any Windows specific code (or a derivative thereof) from
97the apps directory (application code) you must include an acknowledgement: 96 the apps directory (application code) you must include an acknowledgement:
98"This product includes software written by Tim Hudson 97 "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
99(tjh@cryptsoft.com)" 98
100 99 THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
101THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED 100HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
102WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 101
103MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO 102 The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence
104EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 103 [including the GNU Public Licence.]
105INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 104
106LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
107PROFITS; OR BUSINESS INTERRUPTION)
108HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
109LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
110OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
111
112The licence and distribution terms for any publically available version or
113derivative of this code cannot be changed. i.e. this code cannot simply be
114copied and put under another distribution licence
115[including the GNU Public Licence.]
116
117
118
119
120
121 105
122 106
123 107