LICENSE 6.9 KB

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