-
Notifications
You must be signed in to change notification settings - Fork 368
Preparation for ESAPI 2.5.3.0 release #809
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.
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
Conversation
…SA to 2048-bit SHA256withDSA.
…1 year after the official ESAPI 2.5.3.0 release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Straightforward enough.
Sorry I thought I was just approving the first commit. Walking through the changes today. |
src/main/java/org/owasp/esapi/reference/DefaultSecurityConfiguration.java
Show resolved
Hide resolved
src/test/java/org/owasp/esapi/reference/validation/HTMLValidationRuleCleanTest.java
Show resolved
Hide resolved
src/test/java/org/owasp/esapi/reference/validation/HTMLValidationRuleCleanTest.java
Show resolved
Hide resolved
src/test/java/org/owasp/esapi/reference/validation/HTMLValidationRuleCleanTest.java
Show resolved
Hide resolved
I approve, I will wait until EOB for @jeremiahjstacey to take a pass, but this seems mostly routine with just some new tests. |
Okay. I will wait until 7pm ET today until I merge this to give @jeremiahjstacey the opportunity to approve this PR. Of it he doesn't intend reviewing this PR, until he communicates that via a comment in this PR or an email to me. |
All looks good to me. Sorry for the delay. |
@jeremiahjstacey wrote:
No worries. It's all good. Just want to get this out the door while I'm on PTO / Holiday. |
Validator.isValidSafeHTML
interfaces; to be removed in 1 year after ESAPI 2.5.3.0 release.isValidSafeHTML
methods.