| README (100928) | README (100936) |
|---|---|
| 1 | 1 |
| 2 OpenSSL 0.9.6d 9 May 2002 | 2 OpenSSL 0.9.6e 30 July 2002 |
| 3 4 Copyright (c) 1998-2002 The OpenSSL Project 5 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson 6 All rights reserved. 7 8 DESCRIPTION 9 ----------- 10 --- 106 unchanged lines hidden (view full) --- 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 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 use them. Look at the example programs. 124 | 3 4 Copyright (c) 1998-2002 The OpenSSL Project 5 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson 6 All rights reserved. 7 8 DESCRIPTION 9 ----------- 10 --- 106 unchanged lines hidden (view full) --- 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 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 use them. Look at the example programs. 124 |
| 125 PROBLEMS 126 -------- 127 128 For some platforms, there are some known problems that may affect the user 129 or application author. We try to collect those in doc/PROBLEMS, with current 130 thoughts on how they should be solved in a future of OpenSSL. 131 |
|
| 125 SUPPORT 126 ------- 127 128 If you have any problems with OpenSSL then please take the following steps 129 first: 130 131 - Download the current snapshot from ftp://ftp.openssl.org/snapshot/ 132 to see if the problem has already been addressed --- 8 unchanged lines hidden (view full) --- 141 - On other systems: 142 OpenSSL version: output of 'openssl version -a' 143 OS Name, Version, Hardware platform 144 Compiler Details (name, version) 145 - Application Details (name, version) 146 - Problem Description (steps that will reproduce the problem, if known) 147 - Stack Traceback (if the application dumps core) 148 | 132 SUPPORT 133 ------- 134 135 If you have any problems with OpenSSL then please take the following steps 136 first: 137 138 - Download the current snapshot from ftp://ftp.openssl.org/snapshot/ 139 to see if the problem has already been addressed --- 8 unchanged lines hidden (view full) --- 148 - On other systems: 149 OpenSSL version: output of 'openssl version -a' 150 OS Name, Version, Hardware platform 151 Compiler Details (name, version) 152 - Application Details (name, version) 153 - Problem Description (steps that will reproduce the problem, if known) 154 - Stack Traceback (if the application dumps core) 155 |
| 149 Report the bug to the OpenSSL project at: | 156 Report the bug to the OpenSSL project via the Request Tracker 157 (http://www.openssl.org/rt2.html) by mail to: |
| 150 151 openssl-bugs@openssl.org 152 | 158 159 openssl-bugs@openssl.org 160 |
| 153 Note that mail to openssl-bugs@openssl.org is forwarded to a public | 161 Note that mail to openssl-bugs@openssl.org is recorded in the publicly 162 readable request tracker database and is forwarded to a public |
| 154 mailing list. Confidential mail may be sent to openssl-security@openssl.org 155 (PGP key available from the key servers). 156 157 HOW TO CONTRIBUTE TO OpenSSL 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 | 163 mailing list. Confidential mail may be sent to openssl-security@openssl.org 164 (PGP key available from the key servers). 165 166 HOW TO CONTRIBUTE TO OpenSSL 167 ---------------------------- 168 169 Development is coordinated on the openssl-dev mailing list (see 170 http://www.openssl.org for information on subscribing). If you 171 would like to submit a patch, send it to openssl-dev@openssl.org with 172 the string "[PATCH]" in the subject. Please be sure to include a 173 textual explanation of what your patch does. 174 175 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 | 176 if a TSA notification and a copy of the patch is sent to crypt@bis.doc.gov; 177 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic] 178 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)). |
| 168 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 .. 176 # diff -ur openssl-orig openssl-work > mydiffs.patch | 179 180 The preferred format for changes is "diff -u" output. You might 181 generate it like this: 182 183 # cd openssl-work 184 # [your changes] 185 # ./Configure dist; make clean 186 # cd .. 187 # diff -ur openssl-orig openssl-work > mydiffs.patch |