The testConfigChecksum test for the DefaultSecurityConfiguration is not
testing ESAPI per se. It's an example of a best practice, but doesn't e.g.
extract a MD5 value from within ESAPI.xml, and compare that against a
recomputed value. Please remove this test from SecurityConfigurationTest.
Original issue reported on code.google.com by mike.bob...@gmail.com on 9 Oct 2009 at 7:32
Original issue reported on code.google.com by
mike.bob...@gmail.com
on 9 Oct 2009 at 7:32