You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2021. It is now read-only.
Hola, currently a lot of tampers are used. The problem is that some tampers only works with some db and some are not needed in our case ( like the base64encode one )
If you've a suggestion of tamper to blacklist, I would be glad you post it here.
I'm thinking that AutoSQLI should adopt a white-list way of getting tampers.
And I may get rid of the custom WhatWaf tampers (even if they are proven to be effective), because they don't have a priority level assigned to them
The text was updated successfully, but these errors were encountered:
To do this, I created a tampers directory in the root of the project, which in there is a WhatWaf_tampers, a sqlmap_tampers, and a whitelisted_tampers dir.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hola, currently a lot of tampers are used.The problem is that some tampers only works with some db and some are not needed in our case ( like thebase64encode
one )If you've a suggestion of tamper to blacklist, I would be glad you post it here.I'm thinking that AutoSQLI should adopt a white-list way of getting tampers.
And I may get rid of the custom WhatWaf tampers (even if they are proven to be effective), because they don't have a priority level assigned to them
The text was updated successfully, but these errors were encountered: