-
-
Notifications
You must be signed in to change notification settings - Fork 675
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
2.4.1 should be required for L1 #1773
Comments
So you copy-paste selective texts from around documents, but not the one which is written to the mentioned section? :)
Requirement itself:
In general I agree it should be level 1, but based on level description for ASVS v4.0.* it is defined as level 2 and the reason is also described in the section. So at the moment I see it as duplicate of #1495 |
Hehe good point, I should've copied the text from the section (& probably read that it states to "Verify", which of course there's probably someone out there doing 100k md5's and that might be timing-indistinguishable) @Sjord brings up a valid point in that #1495 thread:
I'll continue my separate thought over there, thank you! |
I don't close it at the moment, just marked it as "level question". If we can declare the levels on one nice day, we need to recheck those issues as well. |
We made major changes to password storage in v6, please re-open this if you think I'm closing it prematurely, |
2.4.1
Application Security Verification Levels:
Insecure password storage or insecure credential handling can be tested by a human in at least one method, such as detecting non-timing-safe string comparisons. Secure password hashing is surely testable as a human from a black box and can be inferred to some extent based on response timing.
Using ASVS for Level 1 states:
And insecure password hashing, storage, and non-timing-safe string comparisons surely fall under A02 Cryptographic Failures
The text was updated successfully, but these errors were encountered: