1OpenVPN (TM) -- An Open Source VPN daemon 2 3Copyright (C) 2002-2010 OpenVPN Technologies, Inc. <sales@openvpn.net> 4 5This distribution contains multiple components, some 6of which fall under different licenses. By using OpenVPN 7or any of the bundled components enumerated below, you 8agree to be bound by the conditions of the license for 9each respective component. 10 11OpenVPN trademark 12----------------- 13 14 "OpenVPN" is a trademark of OpenVPN Technologies, Inc. 15 16 17OpenVPN license: 18---------------- 19 20 OpenVPN is distributed under the GPL license version 2 (see Below). 21 22 Special exception for linking OpenVPN with OpenSSL: 23 24 In addition, as a special exception, OpenVPN Technologies, Inc. gives 25 permission to link the code of this program with the OpenSSL 26 library (or with modified versions of OpenSSL that use the same 27 license as OpenSSL), and distribute linked combinations including 28 the two. You must obey the GNU General Public License in all 29 respects for all of the code used other than OpenSSL. If you modify 30 this file, you may extend this exception to your version of the 31 file, but you are not obligated to do so. If you do not wish to 32 do so, delete this exception statement from your version. 33 34LZO license: 35------------ 36 37 LZO is Copyright (C) Markus F.X.J. Oberhumer, 38 and is licensed under the GPL. 39 40 Special exception for linking OpenVPN with both OpenSSL and LZO: 41 42 Hereby I grant a special exception to the OpenVPN project 43 (http://openvpn.net/) to link the LZO library with 44 the OpenSSL library (http://www.openssl.org). 45 46 Markus F.X.J. Oberhumer 47 48TAP-Win32/TAP-Win64 Driver license: 49----------------------------------- 50 51 This device driver was inspired by the CIPE-Win32 driver by 52 Damion K. Wilson. 53 54 The source and object code of the TAP-Win32/TAP-Win64 driver 55 is Copyright (C) 2002-2010 OpenVPN Technologies, Inc., and is released under 56 the GPL version 2. 57 58Windows DDK Samples: 59-------------------- 60 61 The Windows binary distribution includes devcon.exe, a 62 Microsoft DDK sample which is redistributed under the terms 63 of the DDK EULA. 64 65NSIS License: 66------------- 67 68 Copyright (C) 2002-2003 Joost Verburg 69 70 This software is provided 'as-is', without any express or implied 71 warranty. In no event will the authors be held liable for any damages 72 arising from the use of this software. 73 74 Permission is granted to anyone to use this software for any purpose, 75 including commercial applications, and to alter it and redistribute 76 it freely, subject to the following restrictions: 77 78 1. The origin of this software must not be misrepresented; 79 you must not claim that you wrote the original software. 80 If you use this software in a product, an acknowledgment in the 81 product documentation would be appreciated but is not required. 82 2. Altered versions must be plainly marked as such, 83 and must not be misrepresented as being the original software. 84 3. This notice may not be removed or altered from any distribution. 85 86OpenSSL License: 87---------------- 88 89 The OpenSSL toolkit stays under a dual license, i.e. both the conditions of 90 the OpenSSL License and the original SSLeay license apply to the toolkit. 91 See below for the actual license texts. Actually both licenses are BSD-style 92 Open Source licenses. In case of any license issues related to OpenSSL 93 please contact openssl-core@openssl.org. 94 95/* ==================================================================== 96 * Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved. 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 * 102 * 1. Redistributions of source code must retain the above copyright 103 * notice, this list of conditions and the following disclaimer. 104 * 105 * 2. Redistributions in binary form must reproduce the above copyright 106 * notice, this list of conditions and the following disclaimer in 107 * the documentation and/or other materials provided with the 108 * distribution. 109 * 110 * 3. All advertising materials mentioning features or use of this 111 * software must display the following acknowledgment: 112 * "This product includes software developed by the OpenSSL Project 113 * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 114 * 115 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to 116 * endorse or promote products derived from this software without 117 * prior written permission. For written permission, please contact 118 * openssl-core@openssl.org. 119 * 120 * 5. Products derived from this software may not be called "OpenSSL" 121 * nor may "OpenSSL" appear in their names without prior written 122 * permission of the OpenSSL Project. 123 * 124 * 6. Redistributions of any form whatsoever must retain the following 125 * acknowledgment: 126 * "This product includes software developed by the OpenSSL Project 127 * for use in the OpenSSL Toolkit (http://www.openssl.org/)" 128 * 129 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY 130 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 131 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 132 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR 133 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 134 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 135 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 136 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 137 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 138 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 139 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 140 * OF THE POSSIBILITY OF SUCH DAMAGE. 141 * ==================================================================== 142 * 143 * This product includes cryptographic software written by Eric Young 144 * (eay@cryptsoft.com). This product includes software written by Tim 145 * Hudson (tjh@cryptsoft.com). 146 * 147 */ 148 149 Original SSLeay License 150 ----------------------- 151 152/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) 153 * All rights reserved. 154 * 155 * This package is an SSL implementation written 156 * by Eric Young (eay@cryptsoft.com). 157 * The implementation was written so as to conform with Netscapes SSL. 158 * 159 * This library is free for commercial and non-commercial use as long as 160 * the following conditions are aheared to. The following conditions 161 * apply to all code found in this distribution, be it the RC4, RSA, 162 * lhash, DES, etc., code; not just the SSL code. The SSL documentation 163 * included with this distribution is covered by the same copyright terms 164 * except that the holder is Tim Hudson (tjh@cryptsoft.com). 165 * 166 * Copyright remains Eric Young's, and as such any Copyright notices in 167 * the code are not to be removed. 168 * If this package is used in a product, Eric Young should be given attribution 169 * as the author of the parts of the library used. 170 * This can be in the form of a textual message at program startup or 171 * in documentation (online or textual) provided with the package. 172 * 173 * Redistribution and use in source and binary forms, with or without 174 * modification, are permitted provided that the following conditions 175 * are met: 176 * 1. Redistributions of source code must retain the copyright 177 * notice, this list of conditions and the following disclaimer. 178 * 2. Redistributions in binary form must reproduce the above copyright 179 * notice, this list of conditions and the following disclaimer in the 180 * documentation and/or other materials provided with the distribution. 181 * 3. All advertising materials mentioning features or use of this software 182 * must display the following acknowledgement: 183 * "This product includes cryptographic software written by 184 * Eric Young (eay@cryptsoft.com)" 185 * The word 'cryptographic' can be left out if the rouines from the library 186 * being used are not cryptographic related :-). 187 * 4. If you include any Windows specific code (or a derivative thereof) from 188 * the apps directory (application code) you must include an acknowledgement: 189 * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" 190 * 191 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND 192 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 193 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 194 * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 195 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 196 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 197 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 198 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 199 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 200 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 201 * SUCH DAMAGE. 202 * 203 * The licence and distribution terms for any publically available version or 204 * derivative of this code cannot be changed. i.e. this code cannot simply be 205 * copied and put under another distribution licence 206 * [including the GNU Public Licence.] 207 */ 208 209GNU Public License (GPL) 210------------------------ 211 212 OpenVPN, LZO, and the TAP-Win32 distributions are 213 licensed under the GPL version 2 (see COPYRIGHT.GPL). 214 215 In the Windows binary distribution of OpenVPN, the 216 GPL is reproduced below. 217 218