| README (59191) | README (68651) |
|---|---|
| 1 | 1 |
| 2 OpenSSL 0.9.5a 1 Apr 2000 | 2 OpenSSL 0.9.6 24 Sep 2000 |
| 3 4 Copyright (c) 1998-2000 The OpenSSL Project 5 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson 6 All rights reserved. 7 8 DESCRIPTION 9 ----------- 10 --- 83 unchanged lines hidden (view full) --- 94 ------- 95 96 Various companies hold various patents for various algorithms in various 97 locations around the world. _YOU_ are responsible for ensuring that your use 98 of any algorithms is legal by checking if there are any patents in your 99 country. The file contains some of the patents that we know about or are 100 rumoured to exist. This is not a definitive list. 101 | 3 4 Copyright (c) 1998-2000 The OpenSSL Project 5 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson 6 All rights reserved. 7 8 DESCRIPTION 9 ----------- 10 --- 83 unchanged lines hidden (view full) --- 94 ------- 95 96 Various companies hold various patents for various algorithms in various 97 locations around the world. _YOU_ are responsible for ensuring that your use 98 of any algorithms is legal by checking if there are any patents in your 99 country. The file contains some of the patents that we know about or are 100 rumoured to exist. This is not a definitive list. 101 |
| 102 RSA Data Security holds software patents on the RSA and RC5 algorithms. If 103 their ciphers are used used inside the USA (and Japan?), you must contact RSA 104 Data Security for licensing conditions. Their web page is 105 http://www.rsa.com/. | 102 RSA Security holds software patents on the RC5 algorithm. If you 103 intend to use this cipher, you must contact RSA Security for 104 licensing conditions. Their web page is http://www.rsasecurity.com/. |
| 106 | 105 |
| 107 RC4 is a trademark of RSA Data Security, so use of this label should perhaps 108 only be used with RSA Data Security's permission. | 106 RC4 is a trademark of RSA Security, so use of this label should perhaps 107 only be used with RSA Security's permission. |
| 109 110 The IDEA algorithm is patented by Ascom in Austria, France, Germany, Italy, 111 Japan, Netherlands, Spain, Sweden, Switzerland, UK and the USA. They should 112 be contacted if that algorithm is to be used, their web page is 113 http://www.ascom.ch/. 114 115 INSTALLATION 116 ------------ 117 118 To install this package under a Unix derivative, read the INSTALL file. For 119 a Win32 platform, read the INSTALL.W32 file. For OpenVMS systems, read 120 INSTALL.VMS. 121 | 108 109 The IDEA algorithm is patented by Ascom in Austria, France, Germany, Italy, 110 Japan, Netherlands, Spain, Sweden, Switzerland, UK and the USA. They should 111 be contacted if that algorithm is to be used, their web page is 112 http://www.ascom.ch/. 113 114 INSTALLATION 115 ------------ 116 117 To install this package under a Unix derivative, read the INSTALL file. For 118 a Win32 platform, read the INSTALL.W32 file. For OpenVMS systems, read 119 INSTALL.VMS. 120 |
| 122 For people in the USA, it is possible to compile OpenSSL to use RSA Inc.'s 123 public key library, RSAREF, by configuring OpenSSL with the option "rsaref". 124 | |
| 125 Read the documentation in the doc/ directory. It is quite rough, but it 126 lists the functions, you will probably have to look at the code to work out 127 how to used them. Look at the example programs. 128 129 SUPPORT 130 ------- 131 132 If you have any problems with OpenSSL then please take the following steps --- 29 unchanged lines hidden (view full) --- 162 ---------------------------- 163 164 Development is coordinated on the openssl-dev mailing list (see 165 http://www.openssl.org for information on subscribing). If you 166 would like to submit a patch, send it to openssl-dev@openssl.org with 167 the string "[PATCH]" in the subject. Please be sure to include a 168 textual explanation of what your patch does. 169 | 121 Read the documentation in the doc/ directory. It is quite rough, but it 122 lists the functions, you will probably have to look at the code to work out 123 how to used them. Look at the example programs. 124 125 SUPPORT 126 ------- 127 128 If you have any problems with OpenSSL then please take the following steps --- 29 unchanged lines hidden (view full) --- 158 ---------------------------- 159 160 Development is coordinated on the openssl-dev mailing list (see 161 http://www.openssl.org for information on subscribing). If you 162 would like to submit a patch, send it to openssl-dev@openssl.org with 163 the string "[PATCH]" in the subject. Please be sure to include a 164 textual explanation of what your patch does. 165 |
| 166 Note: For legal reasons, contributions from the US can be accepted only 167 if a copy of the patch is sent to crypt@bxa.doc.gov 168 |
|
| 170 The preferred format for changes is "diff -u" output. You might 171 generate it like this: 172 173 # cd openssl-work 174 # [your changes] 175 # ./Configure dist; make clean 176 # cd .. | 169 The preferred format for changes is "diff -u" output. You might 170 generate it like this: 171 172 # cd openssl-work 173 # [your changes] 174 # ./Configure dist; make clean 175 # cd .. |
| 177 # diff -urN openssl-orig openssl-work > mydiffs.patch | 176 # diff -ur openssl-orig openssl-work > mydiffs.patch |