Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DefaultSecurityConfiguration test for checksum is not testing ESAPI #5

Closed
GoogleCodeExporter opened this issue Feb 4, 2016 · 2 comments
Closed

DefaultSecurityConfiguration test for checksum is not testing ESAPI #5

GoogleCodeExporter opened this issue Feb 4, 2016 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

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
@GoogleCodeExporter
Copy link
Author

Original comment by mike.bob...@gmail.com on 9 Oct 2009 at 7:42

@GoogleCodeExporter
Copy link
Author 

Mike,

Fixed - see r130

thanks,
Andrew

Original comment by vande...@gmail.com on 20 Oct 2009 at 11:46

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter