COPYING 9.2 KB

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