LICENSE 7.0 KB

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