-
Notifications
You must be signed in to change notification settings - Fork 3
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
Input Validation - All #234
Comments
I'm burning out too (mostly from other projects now) but I'll take a stab at this |
On wip-commissions I fixed a few of these issues b3f2b1c As it says in the commit message, we're now sanitizing all parameters posted to our site. If there's a problem with this let me know and I can make it page-specific. |
What is the status of this? How many of these input validation issues are currently addressed? |
Sanitation is done so we're good from a security stand point. We have not On Sat, Dec 7, 2013 at 9:34 PM, Christina Quan notifications@github.comwrote:
|
Okay, at least we're good from a security stand point then. Not sure how high-priority field completion checks are. |
Sanitization is done. Closing this. |
Field completion checks are still not implemented. |
Condensed list of pages that need server- and/or client-end input validation (NEVER trust user input!)
These come behind functionality priorities, thus may not make the final release.
In general, all validation should be done by the server, while client-end validation is a good shell for increased user experience and mitigating form data loss.
The text was updated successfully, but these errors were encountered: