summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBodo Möller <bodo@openssl.org>2004-07-12 06:24:58 +0000
committerBodo Möller <bodo@openssl.org>2004-07-12 06:24:58 +0000
commitd385d43e1e47d304b0eb117888ad5f3fad92c12e (patch)
tree1e6864acc42bd16766f0d5fc077ed38ea7c09090
parent4b7693a75e31854f97bb056c84fffe14c0f9cff6 (diff)
BIS correction/addition
-rw-r--r--README16
1 files changed, 11 insertions, 5 deletions
diff --git a/README b/README
index 406e049224..edfee75326 100644
--- a/README
+++ b/README
@@ -173,11 +173,17 @@
textual explanation of what your patch does.
Note: For legal reasons, contributions from the US can be accepted only
- 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
+ if a TSU notification and a copy of the patch are sent to crypt@bis.doc.gov
+ (formerly BXA) with a copy to the ENC Encryption Request Coordinator;
+ please take some time to look at
+ 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))
+ for the details. If "your encryption source code is too large to serve as
+ an email attachment", they are glad to receive it by fax instead; hope you
+ have a cheap long-distance plan.
+
+ Our preferred format for changes is "diff -u" output. You might
generate it like this:
# cd openssl-work