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