From f6f66b33a6d21afe2f57d45f4608660ee6e53387 Mon Sep 17 00:00:00 2001
From: aanganes <aanganes@mitre.org>
Date: Wed, 15 Feb 2012 09:15:08 -0800
Subject: [PATCH] Updated Home (markdown)

---
 Home.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/Home.md b/Home.md
index 9d94af2..b78ac1c 100644
--- a/Home.md
+++ b/Home.md
@@ -20,6 +20,18 @@ with the proper values for your deployment filled in. The project will fail to b
 
 Since this file contains sensitive information (and will vary from deployment to deployment) it should not be checked in.
 
+## JCE
+
+The project uses JCE through BouncyCastle. Your system may be set up to handle this already, in which case no further action is needed. 
+
+If you run into javax.crypto.JceSecurity errors, do the following:
+
+1. Add the BouncyCastle Provider to your JRE/JDK, per instructions at http://www.bouncycastle.org/wiki/display/JA1/Provider+Installation/
+
+2. Download the "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files" for your JRE version from http://www.oracle.com/technetwork/java/javase/downloads/index.html (scroll to the bottom of the page).
+
+3. Install the new policy files per the README file included in the download. The download contains new versions of local_policy.jar and US_export_policy.jar. These files must be placed in your jre/lib/security folder(s - multiple on Windows), replacing the current files. If you wish to at some point revert back to your original policy files, store the original files elsewhere.
+ 
 ### Building ###
 
 Init and update the project sub-modules:
@@ -29,4 +41,4 @@ Init and update the project sub-modules:
 
 You'll need (http://maven.apache.org/)mvn2 installed to build via:
 
-    mvn package
+    mvn package
\ No newline at end of file