You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.md 5.8 kB

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