Closed GoogleCodeExporter closed 9 years ago
I believe this issue has been resolved. Keven can you verify?
Original comment by chrisisbeef
on 2 Dec 2009 at 7:25
This was fixed in ESAPI-2.0rc3 release.
Using ESAPI with Encryptor.MasterKey or Encryptor.MasterSalt
being either missing or empty in the ESAPI.properties file now
results in a ConfigurationException being thrown.
Furthermore, the ESAPI.properties file is now shipped this way be
default to force developers to generate their own master key and salt
by executing JavaEncryptor.main(). The exact instructions on how to
do this are in the ESAPI.properties file.
Depending on how you are using ESAPI, this may or may not be logged.
Original comment by kevin.w.wall@gmail.com
on 3 Dec 2009 at 1:11
Original issue reported on code.google.com by
mikael....@gmail.com
on 3 Sep 2009 at 9:23