summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBodo Möller <bodo@openssl.org>2004-07-11 08:58:43 +0000
committerBodo Möller <bodo@openssl.org>2004-07-11 08:58:43 +0000
commit235dee1421846c2687f0d72615540a24031039d0 (patch)
treedaf4d2ef8798ed66ca6c2a41834656d464b154d8
parentd28f7bc74d1baf48d5eb83caa7f6832ebab4dc1d (diff)
downloadopenssl-new-235dee1421846c2687f0d72615540a24031039d0.tar.gz
BIS correction/addition
-rw-r--r--README16
1 files changed, 11 insertions, 5 deletions
diff --git a/README b/README
index 0c242c7ef2..0b38e7f1d1 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 a 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