COPYING

   1 OpenVPN (TM) -- An Open Source VPN daemon
   2
   3 Copyright (C) 2002-2023 OpenVPN Inc <sales@openvpn.net>
   4
   5 This distribution contains multiple components, some
   6 of which fall under different licenses.  By using OpenVPN
   7 or any of the bundled components enumerated below, you
   8 agree to be bound by the conditions of the license for
   9 each respective component.
  10
  11 OpenVPN trademark
  12 -----------------
  13
  14   "OpenVPN" is a trademark of OpenVPN Inc
  15
  16
  17 OpenVPN 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 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
  34 Apache2 linking exception:
  35 ---------------------------
  36 OpenVPN is currently undergoing a license change to add an exception for
  37 Apache 2 linking. The following exception is only valid for new contributions
  38 after 2023-05-03 and past contribution where the authors have already agreed
  39 to the exception.
  40
  41   In addition, as a special exception, OpenVPN Inc and the
  42   contributors give permission to link the code of this program to
  43   libraries (the "Libraries") licensed under the Apache License
  44   version 2.0 (this work and any linked library the "Combined Work")
  45   and copy and distribute the Combined Work without an obligation to
  46   license the Libraries under the GNU General Public License v2
  47   (GPL-2.0) as required by Section 2 of the GPL-2.0, and without an
  48   obligation to refrain from imposing any additional restrictions in
  49   the Apache License version 2 that are not in the GPL-2.0, as
  50   required by Section 6 of the GPL-2.0.  You must comply with the
  51   GPL-2.0 in all other respects for the Combined Work, including
  52   the obligation to provide source code.  If you modify this file, you
  53   may extend this exception to your version of the file, but you are
  54   not obligated to do so.  If you do not wish to do so, delete this
  55   exception statement from your version.
  56
  57 For better understanding, in plain non-legalese English this basically says:
  58
  59  * The intention for this license exception is to allow OpenVPN to be
  60    linked against APL-2 licensed libraries, even where the GPL-2.0 and
  61    APL-2 licenses conflict from a legal perspective.
  62
  63  * OpenVPN itself will stay GPL-2.0 and the code belonging to the
  64    OpenVPN project must comply to the GPL-2.0 license.  This is NOT
  65    dual-licensing of the OpenVPN code base.
  66
  67  * This license exception DOES NOT require NOR expect a license change
  68    of the APL-2 based library.  This exception allows using the APL-2
  69    library as-is.  However, when distributing a compiled OpenVPN binary
  70    linking against APL-2 libraries ("Combined Work"), the REQUIREMENT is
  71    that the APL-2 library MUST also be available on similar terms as in
  72    GPL-2.0, like providing the source code of the library upon request,
  73    except in the two specific ways mentioned.
  74
  75  * If the APL-2 based library forbids such linking and distribution,
  76    this license exception DOES NOT overrule the restriction of the APL-2
  77    based library.  If the APL-2 library cannot satisfy the requirements
  78    in this license exception, you CANNOT distribute an OpenVPN binary
  79    linked with this library.
  80
  81 LZO license:
  82 ------------
  83
  84   LZO is Copyright (C) Markus F.X.J. Oberhumer,
  85   and is licensed under the GPL.
  86
  87   Special exception for linking OpenVPN with both OpenSSL and LZO:
  88
  89   Hereby I grant a special exception to the OpenVPN project
  90   (http://openvpn.net/) to link the LZO library with
  91   the OpenSSL library (http://www.openssl.org).
  92
  93   Markus F.X.J. Oberhumer
  94
  95 TAP-Win32/TAP-Win64 Driver license:
  96 -----------------------------------
  97
  98   This device driver was inspired by the CIPE-Win32 driver by
  99   Damion K. Wilson.
 100
 101   The source and object code of the TAP-Win32/TAP-Win64 driver
 102   is Copyright (C) 2002-2018 OpenVPN Inc, and is released under
 103   the GPL version 2.
 104
 105 Windows DDK Samples:
 106 --------------------
 107
 108   The Windows binary distribution includes devcon.exe, a
 109   Microsoft DDK sample which is redistributed under the terms
 110   of the DDK EULA.
 111
 112 NSIS License:
 113 -------------
 114
 115   Copyright (C) 2002-2003 Joost Verburg
 116
 117   This software is provided 'as-is', without any express or implied
 118   warranty. In no event will the authors be held liable for any damages
 119   arising from the use of this software.
 120
 121   Permission is granted to anyone to use this software for any purpose,
 122   including commercial applications, and to alter it and redistribute
 123   it freely, subject to the following restrictions:
 124
 125   1. The origin of this software must not be misrepresented;
 126      you must not claim that you wrote the original software.
 127      If you use this software in a product, an acknowledgment in the
 128      product documentation would be appreciated but is not required.
 129   2. Altered versions must be plainly marked as such,
 130      and must not be misrepresented as being the original software.
 131   3. This notice may not be removed or altered from any distribution.
 132
 133 OpenSSL License:
 134 ----------------
 135
 136   The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
 137   the OpenSSL License and the original SSLeay license apply to the toolkit.
 138   See below for the actual license texts. Actually both licenses are BSD-style
 139   Open Source licenses. In case of any license issues related to OpenSSL
 140   please contact openssl-core@openssl.org.
 141
 142 /* ====================================================================
 143  * Copyright (c) 1998-2003 The OpenSSL Project.  All rights reserved.
 144  *
 145  * Redistribution and use in source and binary forms, with or without
 146  * modification, are permitted provided that the following conditions
 147  * are met:
 148  *
 149  * 1. Redistributions of source code must retain the above copyright
 150  *    notice, this list of conditions and the following disclaimer.
 151  *
 152  * 2. Redistributions in binary form must reproduce the above copyright
 153  *    notice, this list of conditions and the following disclaimer in
 154  *    the documentation and/or other materials provided with the
 155  *    distribution.
 156  *
 157  * 3. All advertising materials mentioning features or use of this
 158  *    software must display the following acknowledgment:
 159  *    "This product includes software developed by the OpenSSL Project
 160  *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
 161  *
 162  * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
 163  *    endorse or promote products derived from this software without
 164  *    prior written permission. For written permission, please contact
 165  *    openssl-core@openssl.org.
 166  *
 167  * 5. Products derived from this software may not be called "OpenSSL"
 168  *    nor may "OpenSSL" appear in their names without prior written
 169  *    permission of the OpenSSL Project.
 170  *
 171  * 6. Redistributions of any form whatsoever must retain the following
 172  *    acknowledgment:
 173  *    "This product includes software developed by the OpenSSL Project
 174  *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
 175  *
 176  * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
 177  * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 178  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 179  * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
 180  * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 181  * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 182  * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 183  * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 184  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 185  * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 186  * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 187  * OF THE POSSIBILITY OF SUCH DAMAGE.
 188  * ====================================================================
 189  *
 190  * This product includes cryptographic software written by Eric Young
 191  * (eay@cryptsoft.com).  This product includes software written by Tim
 192  * Hudson (tjh@cryptsoft.com).
 193  *
 194  */
 195
 196  Original SSLeay License
 197  -----------------------
 198
 199 /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
 200  * All rights reserved.
 201  *
 202  * This package is an SSL implementation written
 203  * by Eric Young (eay@cryptsoft.com).
 204  * The implementation was written so as to conform with Netscapes SSL.
 205  *
 206  * This library is free for commercial and non-commercial use as long as
 207  * the following conditions are aheared to.  The following conditions
 208  * apply to all code found in this distribution, be it the RC4, RSA,
 209  * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 210  * included with this distribution is covered by the same copyright terms
 211  * except that the holder is Tim Hudson (tjh@cryptsoft.com).
 212  *
 213  * Copyright remains Eric Young's, and as such any Copyright notices in
 214  * the code are not to be removed.
 215  * If this package is used in a product, Eric Young should be given attribution
 216  * as the author of the parts of the library used.
 217  * This can be in the form of a textual message at program startup or
 218  * in documentation (online or textual) provided with the package.
 219  *
 220  * Redistribution and use in source and binary forms, with or without
 221  * modification, are permitted provided that the following conditions
 222  * are met:
 223  * 1. Redistributions of source code must retain the copyright
 224  *    notice, this list of conditions and the following disclaimer.
 225  * 2. Redistributions in binary form must reproduce the above copyright
 226  *    notice, this list of conditions and the following disclaimer in the
 227  *    documentation and/or other materials provided with the distribution.
 228  * 3. All advertising materials mentioning features or use of this software
 229  *    must display the following acknowledgement:
 230  *    "This product includes cryptographic software written by
 231  *     Eric Young (eay@cryptsoft.com)"
 232  *    The word 'cryptographic' can be left out if the rouines from the library
 233  *    being used are not cryptographic related :-).
 234  * 4. If you include any Windows specific code (or a derivative thereof) from
 235  *    the apps directory (application code) you must include an acknowledgement:
 236  *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
 237  *
 238  * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
 239  * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 240  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 241  * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 242  * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 243  * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 244  * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 245  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 246  * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 247  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 248  * SUCH DAMAGE.
 249  *
 250  * The licence and distribution terms for any publically available version or
 251  * derivative of this code cannot be changed.  i.e. this code cannot simply be
 252  * copied and put under another distribution licence
 253  * [including the GNU Public Licence.]
 254  */
 255
 256 GNU Public License (GPL)
 257 ------------------------
 258
 259   OpenVPN, LZO, and the TAP-Win32 distributions are
 260   licensed under the GPL version 2 (see COPYRIGHT.GPL).
 261
 262   In the Windows binary distribution of OpenVPN, the
 263   GPL is reproduced below.
 264