projects
/
openssl.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
For the platforms where version info is inserted separately into the
[openssl.git]
/
README
diff --git
a/README
b/README
index ef9fcc002b392bc66ed2e85932ec1848473af8e4..cfac87fdd8b28f419ef28a910be7d9b3296e1a12 100644
(file)
--- a/
README
+++ b/
README
@@
-122,6
+122,13
@@
lists the functions; you will probably have to look at the code to work out
how to use them. Look at the example programs.
lists the functions; you will probably have to look at the code to work out
how to use them. Look at the example programs.
+ PROBLEMS
+ --------
+
+ For some platforms, there are some known problems that may affect the user
+ or application author. We try to collect those in doc/PROBLEMS, with current
+ thoughts on how they should be solved in a future of OpenSSL.
+
SUPPORT
-------
SUPPORT
-------
@@
-146,11
+153,13
@@
- Problem Description (steps that will reproduce the problem, if known)
- Stack Traceback (if the application dumps core)
- Problem Description (steps that will reproduce the problem, if known)
- Stack Traceback (if the application dumps core)
- Report the bug to the OpenSSL project at:
+ Report the bug to the OpenSSL project via the Request Tracker
+ (http://www.openssl.org/rt2.html) by mail to:
openssl-bugs@openssl.org
openssl-bugs@openssl.org
- Note that mail to openssl-bugs@openssl.org is forwarded to a public
+ Note that mail to openssl-bugs@openssl.org is recorded in the publicly
+ readable request tracker database and is forwarded to a public
mailing list. Confidential mail may be sent to openssl-security@openssl.org
(PGP key available from the key servers).
mailing list. Confidential mail may be sent to openssl-security@openssl.org
(PGP key available from the key servers).
@@
-164,7
+173,9
@@
textual explanation of what your patch does.
Note: For legal reasons, contributions from the US can be accepted only
textual explanation of what your patch does.
Note: For legal reasons, contributions from the US can be accepted only
- if a copy of the patch is sent to crypt@bxa.doc.gov
+ if a TSA notification and a copy of the patch is sent to crypt@bis.doc.gov;
+ see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
+ and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
The preferred format for changes is "diff -u" output. You might
generate it like this:
The preferred format for changes is "diff -u" output. You might
generate it like this: