[Esapi-user] [OWASP-ESAPI] Issues with Encryption api..
nishi787 at hotmail.com
Thu Oct 28 08:23:18 EDT 2010
Thanks Kevin I got version 2.0 encryption api's to work. We had some concern about the key being in the properties file and how to protect the key. Is there any use case that you can point me where somebody used the OWASP 2.0 encryption api's and how did they go about protecting the key specially if the product needs to installed on the customer site.
OWASP Global Education Committee
> Date: Mon, 25 Oct 2010 01:21:37 -0400
> From: kevin.w.wall at gmail.com
> To: nishi787 at hotmail.com
> CC: jim.manico at owasp.org; esapi-user at lists.owasp.org
> Subject: Re: [OWASP-ESAPI] Issues with Encryption api..
> On 10/24/2010 10:18 PM, Nishi Kumar wrote:
> > Thanks for your response. Yes it is in esapi4java-core-2.0-install-guide.doc I have highlighted the line in red.
> > "You MUST replace the ESAPI Encryptor.MasterKey and Encryptor.MasterSalt in ESAPI.properties with ones you personally generate. By default, the ESAPI.properties file has neither of these set and therefore any many encryption related things will fail until you properly set them. Change them now by using:
> > cd <directory containing ESAPI jar>
> > java -classpath ESAPI-2.0rc2.jar org.owasp.esapi.reference.JavaEncryptor
> > The final lines of output from this will look something like:
> > Copy and paste this into ESAPI.properties
> > Encryptor.MasterKey=<something here>
> > Encryptor.MasterSalt=<something here>"
> OK, I fixed that a bit earlier. Just wanted to confirm that's all there was wrt
> documentation. If you get a new version of
> from SVN, you will see the changes.
> > I am trying to use ESAPI encryption api's to encrypt Tomcat database userid and password
> > that is either set in context.xml or server.xml. It is working great with
> > ESAPI 1.4 version of encrypt and decrypt methods.
> > I was trying to use 2.0 version of encrypt and decrypt but was having some
> > difficulty getting it to work. To be able to encrypt and decrypt I have to
> > extend BasicDataSourceFactory class of Tomcat and provide my own
> > implementation of the class which decrypts the userid password. The
> > issue I am having is after encrypting I need to get the string that is
> > used in context.xml and then in BasicDataSourceFactory the encrypted
> > value comes as string that needs to be converted into CipherText so
> > that it can be decrypted. Can you please point me to a sample where I
> > can encrypt/dycrypt from a string and my final output is a String .
> Two good places to look are:
> 1) src/examples/java/PersistedEncryptedData.java
> and the corresponding script to execute this,
> 2) The documentation "ESAPI 2.0 Symmetric Encryption User Guide"
> described in
> In ESAPI 2.0RC10, August Detlefsen also created a new reference implementation
> for EncryptedProperties called ReferenceEncryptedProperties that actually
> extends java.util.Properties. The class java.util.Properties hash methods
> called loadFromXML() and storeToXML(). Sounds like that class might be a
> good match for what you are looking for.
> > Do you think it is just better to use 1.4 api's in this situation. Though
> > 1.4 api's are deprecated so I am guessing eventually it will be removed.
> If you read over the "Why Is OWASP Changing ESAPI Encryption?" discussed in
> it describes how even these deprecated Encryptor methods are not completely
> compatible with those from ESAPI 1.4. Furthermore, if you use these deprecated
> methods, you will not be provided with any protection from the padded oracle
> attack which recently made the news for ASP.NET and JSF not too many weeks ago.
> So I'd recommend using the new methods if you can possibly get them to work.
> If you have any questions after reading the documentation and examples that
> I've referenced, then drop me another email and perhaps attach your sample
> code and I'll take a look at it.
> Kevin W. Wall
> "The most likely way for the world to be destroyed, most experts agree,
> is by accident. That's where we come in; we're computer professionals.
> We cause accidents." -- Nathaniel Borenstein, co-creator of MIME
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Esapi-user