diff options
author | bodo <bodo> | 2004-07-12 06:24:58 +0000 |
---|---|---|
committer | bodo <bodo> | 2004-07-12 06:24:58 +0000 |
commit | 22ed36341d4e7e9e24c25352836329ab32e54203 (patch) | |
tree | 98790fb38f45262890b0785445edca669dd28bec | |
parent | 3bd8b312b975f11c5e3ced781de1818d61fd49d0 (diff) | |
download | openssl-22ed36341d4e7e9e24c25352836329ab32e54203.tar.gz |
BIS correction/additionMERGED_stable2engine-stable
-rw-r--r-- | README | 16 |
1 files changed, 11 insertions, 5 deletions
@@ -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 |