LICENSE 6.8 KB

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